Parse compiled ACS

[eevee]

You might think that's ridiculous, but I'm already 60% of the way there! I don't handle loops or other jump constructs yet, but for a straightforward "do multiple things" script I can tell you exactly what specials are called with what arguments — even if the arguments are script arguments, or come from a global array. All determined statically, no evaluation required.

The goal is to be able to do all of this stuff even for maps without source code available:

• [ ] Detect the type of script arguments, based on what specials they're passed to
• [ ] For a line that executes a script, identify what sectors it affects and highlight them
• [ ] Be able to check for scripts that don't exist (#383)
• [ ] Identify init specials used in OPEN scripts (we already do this, but based on parsing ACS source)
• [ ] Be able to detect doors and lifts even when they're only activated from scripts, for purposes of texture checks (#383) and accessibility checks (#382) and the like

[Gaerzi]

That's interesting. You're focusing on the map editor side of things, but the first use for this feature would be offering a built-in script decompiler/disassembler.

[eevee]

That... is... rather a lot harder, but feasible. And has been done before.