AI_Slop/fs2port
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Docs updated.

Browse source
This commit is contained in:
Scott Duensing 2026-05-14 10:21:11 -05:00
parent b4ddd15710
commit fe725ea6b5
1 changed files with 6 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
ARCHITECTURE.md
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 the dogfight logic would require disassembling that scenery file's opcode
stream — outside the scope of the binary disassembly. 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 `src/chunk5.s:12634` carries an "Unused???" annotation over a block that
subdivision counters in `$2B`) only fully make sense when seen with real transitions `WarDeclared` from `$01` to `$03`, calls `DrawMultiMessage` twice,
scenery byte streams. The handlers in chunk5 are byte-faithful to the source, and busy-waits through a 65k-iteration delay. No code path reaches it in
but their exact intended payload formats would benefit from cross-referencing the current disassembly — possibly an aborted post-war or game-over screen
with the on-disk scenery files. that was never wired up.
### 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.
--- ---