Nothing that needs the game data. Terrain checks (a unit on ground it cannot stand
on), building counts, map pictures and the terrain tools need the tilesets and unit
tables that only the editor has. mapStatistics and validateScenario take null for
them and leave those parts out, as the command line does. The decoders are here, but no
game file is: scmjs map preview reads the tileset out of your copy of StarCraft and
draws with it.
No plugin API. The functions are the editor's, not api.*; a plugin's code does not
run here. A plugin can share logic with a script by putting it in a module both import.
One language. The library's own text — a warning, an issue — is English.
Map text is bytes. Strings come and go in the map's encoding (changeTextEncoding
switches it) and keep their colour codes; plainText strips them for display.
