Investigation notes · Scenario JSON · Opcode directory · Setup checks · Native block disassembly and checks · Message conditions · City explorer
Demo scenarios and test radio messages (earlier script formats)
Objects: cyan = initially active, gold = reserve queue, pink = free-list group. Cell-state lists: orange/red outlines. Stored coordinates only: native setup and underground route snapping can change placements. Overlaps can be inspected through the dropdown.
Script-directed aircraft attacks, not existing damage. Delays, waits, reinforcement activation and interception affect whether they happen. Markers show aiming cells, not blast areas or flight paths. Click a diamond or select a target below; Shift-click still selects aircraft.
Green L: launch / entry. Magenta D: destination. A combined L/D marker means the same cell serves both roles.
Green lines/arrows: sampled native movement. Red cells: scripted map damage (click or select below). Routes start at vehicle activation, including reserve vehicles; they are not a simultaneous mission timeline. Combat and particles are omitted, branch loops show one pass.
Native persistent-state eligibility by map and type · Save-file viewer/editor · Native flight/collision traces
Click an outlined map cell or choose below. The key shows models after the combined list writes, starting from state 00h. Later scripts, alternate-state bits and native setup may change the runtime result. Click a type to highlight its cells. Shift-click the map to select an overlapping object.
Click a type to highlight its placements. Counts include all stored groups, including reserves and free-list objects; these are not necessarily present together in flight.
Select an object.
Formatted multilingual text and commands. Pages and in-flight messages are separated below, with script conditions where the association can be established.
Beacon failure inventory and native blackout replay
Controlled supply-cycle trace: motion, scripts and messages
Static instruction inventory from recovered entry points, not execution order. Conditional loops, runtime state and presentation data still matter.
| Offset | Operation | Operands / references |
|---|