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

re: the flat entity count is explained -- arrivals are not spawns

Browse Source 
Built-in 12 activate_unit returns 0 when the live object is NULL: it registers an
object that already exists and cannot create one. So a wave arrival is a craft
reaching a point on its route, not a new record, and a count of entity records
was never going to move.

Stage 02's UnitGroup totals Count = 116 across 111 squadrons, matching the live
probe's flat 116. The natural objection is that 116 might match by accident --
it does not: across all 28 stages the roster totals run 2..116, and 116 is the
MAXIMUM and unique to Stage 02, with nothing else within 5.

Three independent things agree: the handler cannot spawn, the roster totals 116,
and the live count sits at 116 while 22 of 113 routed squadrons have a route
starting after t=0.

Still n=1 for the per-member identity (only a Stage 02 save exists), and this
cannot settle timetable-vs-event -- that needs a position probe, not a count.
This commit is contained in:
Sylpheed RE agent
2026-08-26 04:59:32 +00:00
parent d986a8564c
commit 67671e68d1
2 changed files with 53 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/re/BACKLOG.md
View File

@@ -392,9 +392,13 @@ search cannot find a *schedule*.
start of that route's *phase* (phase 2 has all 37 routes at t=0). Stage 02
phase 1: 25 at t=0, then 3/3/3/2/1 at t=90/120/170/210/240. 🔴 A live count of
`0x820af030` entity records is FLAT at 116 for 210 s — no arrivals visible.
🟡 116 is exactly Stage 02's roster member count, suggesting one pre-allocated
record per member (n=1, NOT promoted; the refutation needs another stage's
save, which we do not have — only slot 01 / Stage 02 exists).
✅ **2026-08-26: the flat count is explained, not merely refuted.** Built-in 12
`activate_unit` returns immediately when the live object is NULL — it registers
an existing object and cannot spawn one, so arrivals are route positions, not
new records. Stage 02's roster totals 116, and **116 is the maximum across all
28 stages and unique to Stage 02**, so the match is not a common-number
coincidence. 🟡 still n=1 for the per-member identity. ❌ This cannot settle
timetable-vs-event — a position probe is needed, not a count.
✅ **Settled 2026-08-26: `t` is SECONDS.** Consecutive route keyframes give an
implied speed; checked against the live-measured player ceiling (~1530 world
units/s), **0 of 1 104** pairs exceed it under seconds while 89–94 % do under