TrigScript 4.0.1

README.md

@@ -2026,6 +2026,13 @@ a message that says so; none is passed over in silence:
 | Writing a unit's position, cloak or tint | the game refuses these itself (*Units*) |
 | Playing on the classic game (1.16.1) | `trigger()` only |
 
+### Coming from 4.0
+
+Nothing of the language has changed. 4.0.1 builds a script with a long list known when it
+is built, such as a video played in the fog: 4.0.0 refused one of more than 16,384 values
+wider than six bits ("arrays and stacks of … cells, past the 65536"), and now reads it
+where it is in the map, four bytes a value.
+
 ### Coming from 3.12
 
 A 3.12 script builds into the same map, and its programs now build *without eudplib*:

package.json

@@ -1,6 +1,6 @@
 {
   "name": "scmjs-plugin-trigscript",
-  "version": "4.0.0",
+  "version": "4.0.1",
   "private": true,
   "description": "TrigScript — TypeScript that builds into triggers; a plugin for the scmJS StarCraft map editor.",
   "author": "Jeany",

plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "TrigScript",
   "id": "trigscript",
-  "version": "4.0.0",
+  "version": "4.0.1",
   "description": "TypeScript kept inside the map. Ordinary TypeScript — files, imports, helpers, loops — runs when the script is applied and records one trigger per trigger() call: ordinary triggers that play on every version. Code inside program(() => { … }) runs in the game — variables, loops, functions, sleep — and is built into the map by TrigScript itself when you save; a map with a program needs StarCraft: Remastered. Checked as you type against the map's own names, with a built-in simulator.",
   "author": "Jeany",
   "homepage": "https://github.com/scm-js/plugin-trigscript",

version.ts

@@ -5,4 +5,4 @@
  * has been compiled into the editor (`compile.ts`). `tests/script.test.ts` keeps this
  * equal to the manifest's.
  */
-export const VERSION = "4.0.0";
+export const VERSION = "4.0.1";