fabi/Syplheed-Reborn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

re: unit definitions are parsed at stage load, not on wave spawn

Browse Source 
Counted the definition objects at three points in Stage 02 -- just after
take-off, ~12 min into combat, and after GAME OVER: 14 objects, same 14 IDs
each time. Capturing a stage therefore costs one load and one snapshot; the
mission does not have to be played or survived.
This commit is contained in:
Claude (auto-RE)
2026-07-29 17:31:45 +00:00
parent 2fa4c33d1a
commit 2196ac112d
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/re/structures/unit-struct-runtime.md
View File

@@ -219,4 +219,10 @@ tutorial adds its own units; `unit_runtime.py` unions any number of snapshots
and re-solves, and more units directly promote the 🟡 bindings to ✅ by adding and re-solves, and more units directly promote the 🟡 bindings to ✅ by adding
distinct values. distinct values.
**A stage's whole unit set is parsed at load, not as waves spawn** — checked by
counting the definition objects at three points in Stage 02: immediately after
take-off, ~12 minutes in mid-combat, and after GAME OVER. 14 objects, the same
14 IDs, every time. So capturing a stage costs one load and one snapshot; there
is no need to play it, and no need to survive it.
Stages captured so far: `Ttrl` (BASIC CONTROLS), Stage 02. Stages captured so far: `Ttrl` (BASIC CONTROLS), Stage 02.