Docs updated.

This commit is contained in:
Scott Duensing 2026-05-14 10:21:11 -05:00
parent b4ddd15710
commit fe725ea6b5

View file

@ -1400,21 +1400,13 @@ loaded via `PatchSlot_PreMode → LoadSceneryFile1`. To fully reverse-engineer
the dogfight logic would require disassembling that scenery file's opcode
stream — outside the scope of the binary disassembly.
### 17.2 Some Opcode Edge Cases
### 17.2 Unreached `WarDeclared = 3` Block
A few scenery-data records (the COM `$1E` variable-length records, the curve
subdivision counters in `$2B`) only fully make sense when seen with real
scenery byte streams. The handlers in chunk5 are byte-faithful to the source,
but their exact intended payload formats would benefit from cross-referencing
with the on-disk scenery files.
### 17.3 Easter Eggs
`TrimDown` (R key) does `inc $08C8` which triggers `ShowWarReport`. This
appears to be either a developer test-bind or an intentional easter egg.
Similarly, `WarDeclared` gets transitioned to `3` in an unreached code block
at `src/chunk5.s:12590` annotated "unused???" — possibly an aborted
post-war or game-over screen.
`src/chunk5.s:12634` carries an "Unused???" annotation over a block that
transitions `WarDeclared` from `$01` to `$03`, calls `DrawMultiMessage` twice,
and busy-waits through a 65k-iteration delay. No code path reaches it in
the current disassembly — possibly an aborted post-war or game-over screen
that was never wired up.
---