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

re: the reactive-chatter rule table behind ORDOR_SQUADRON_EXTENDED

Browse Source 
864 records = 144 rule tables per language pack x 6.  One schema for all
9216 event records; MessageCount*2 == positional count with zero mismatches.
Named 136/144 by two independent routes that agree as sets.  2388/2405
message ids join the settled sound-cue table.

Corrects squadron-orders.md: the executable misspells all four SQUADRON
entries of the 0x820AEEB0 enum as ORDOR_, and the disc data matches.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE
This commit is contained in:
Claude (auto)
2026-08-27 16:07:17 +00:00
parent d1368c12db
commit 2c2af7ad78
6 changed files with 783 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/re/structures/squadron-orders.md
View File

@@ -57,11 +57,21 @@ as 🟡 rather than levelled up to match the other three.
## 🔴 A different enum that is NOT this
`sub_82320B48` selects a voice line from
`ORDER_{WINGMAN,SQUAD,SQUADRON}_{FORMATION,ATTACK,COVER,EXTENDED}`
(`0x820AEEB0`…). The names are tempting — ATTACK and COVER look like they should
map onto the order classes — but there is **no evidence** they index the order
types, and it is a UI/comms axis. Not connected; do not conflate them.
`sub_82320B48` selects a voice line from twelve strings at `0x820AEEB0`…. Note
the spelling, which is the game's own and matters because it is the join key:
the WINGMAN and SQUAD names are `ORDER_`, and **all four SQUADRON names are
misspelled `ORDOR_`** — `ORDOR_SQUADRON_{FORMATION,ATTACK,COVER,EXTENDED}`. (An
earlier revision of this document rendered all twelve as `ORDER_`.)
The names are tempting — ATTACK and COVER look like they should map onto the
order classes — but there is **no evidence** they index the order types, and it
is a UI/comms axis. Not connected; do not conflate them.
**✅ Settled 2026-08-27, and the warning above holds.** All twelve are record
names in the reactive-chatter rule table, carrying the same misspelling on the
data side — see [`preset-message-rules.md`](preset-message-rules.md). They are
the twelve *events* "a squadron order was issued", each with its own lines,
priority and interval. Triggers for barks, not order types.
## 🟡 Not settled