431461a175
re: BLOCKED -- the 2D / READY_ROOM TOC names, three routes closed with controls
Sylpheed RE agent
2026-08-27 15:22:13 +00:00
4e9d7deeb8
re: which archives the disc can name -- 100% for menu paks, 0.0% for the 2D paks and READY_ROOM
Sylpheed RE agent
2026-08-27 15:08:24 +00:00
152704afeb
re: the in-game HUD config -- 16 records, 419 asset paths, a per-stage ResourceTable
Sylpheed RE agent
2026-08-27 14:53:49 +00:00
8f3973b1c9
re: the variant reading is refuted; HudResource is the in-game screen config
Sylpheed RE agent
2026-08-27 14:42:20 +00:00
4d9f7ce563
re: an embedded .prt part is a top-level RATC bundle, addressed by its element prefix
Sylpheed RE agent
2026-08-27 14:27:38 +00:00
dc868e14c3
re: who references a .prt decides whether it ships -- menu named, in-game embedded
Sylpheed RE agent
2026-08-27 14:13:41 +00:00
da82f8efba
re: where .prt screen parts live; the five mission banners are a real exception
Sylpheed RE agent
2026-08-27 14:01:24 +00:00
8a3c606706
re: correction -- the dialogue table was already in the corpus, and one negative was false
Sylpheed RE agent
2026-08-27 13:45:35 +00:00
e8158f2dfd
re: Stage\script.tbl's 11 non-MISSION fields, and the mission dialogue table
Sylpheed RE agent
2026-08-27 13:37:31 +00:00
0ae0d4bca4
re: the stage numbering is consistent everywhere; the manifest still declares the cut S17
Sylpheed RE agent
2026-08-27 13:27:19 +00:00
caaa3193f6
re: the disc's stage numbers, and the player's craft per stage
Sylpheed RE agent
2026-08-27 13:18:42 +00:00
0ea52c0f48
re: who selects a loadout -- the pak entry does; the Arsenal pak is stage-scoped
Sylpheed RE agent
2026-08-27 13:09:07 +00:00
01a5ed0e29
re: the Hangar loadout system -- loadout, allow-list, arsenal item
Sylpheed RE agent
2026-08-27 12:58:53 +00:00
2519427bab
re: the 59-of-131 arsenal question is closed -- an item names a hardpoint
Sylpheed RE agent
2026-08-27 12:49:22 +00:00
9281aa7456
re: the destructible-subsystem model -- a unit's sub-records
Sylpheed RE agent
2026-08-27 12:39:50 +00:00
9abed411ce
re: correction -- Generic is a per-FILE header record, not a table
Sylpheed RE agent
2026-08-27 12:29:30 +00:00
1bcea1fd49
re: the static unit datasheet and the AI flight model
Sylpheed RE agent
2026-08-27 12:20:03 +00:00
68676d266b
re: the static weapon datasheet -- Weapon, Shell, AssortMissileParam
Sylpheed RE agent
2026-08-27 12:11:03 +00:00
d082ef15ee
re: decode the config records -- render/input constants, and a correction
Sylpheed RE agent
2026-08-27 12:02:13 +00:00
37cb1b49d6
re: the config sections are real disc data -- 64/65, with a clean 0/54 control
Sylpheed RE agent
2026-08-27 11:54:36 +00:00
491c66e742
re: Stage30-33 do not exist; AIParams is missing for exactly the tutorials
Sylpheed RE agent
2026-08-27 11:40:29 +00:00
e00ddd96fa
re: the section reader is a generic IDXD accessor; UNIT_MAX absence re-tested
Sylpheed RE agent
2026-08-27 11:33:30 +00:00
098f9d2ece
re: the config is an INI that ships nearly empty -- every stage takes 200/20
Sylpheed RE agent
2026-08-27 11:24:01 +00:00
4995e1f24a
re: STAGENN_UNIT_MAX holds two per-stage caps, PLANE and VESSEL
Sylpheed RE agent
2026-08-27 11:14:17 +00:00
6fff20e54b
re: X+12 is a 0-based STAGE INDEX -- proved by the game's own string table
Sylpheed RE agent
2026-08-27 11:05:50 +00:00
685e1d41b4
re: a script load builds TWO phase objects, main at Y+4 and demo at Y+8
Sylpheed RE agent
2026-08-27 10:14:00 +00:00
cbf54c9d21
re: the ScriptPhase vtable is 113 slots, and there is a SilphScriptPhaseDemo
Sylpheed RE agent
2026-08-27 10:05:01 +00:00
084ce60bf7
re: the GamePart_MainGame vtable names the code region; a stage-index lead
Sylpheed RE agent
2026-08-27 09:56:34 +00:00
abbd0cfb32
re: the (16,32] gate is != 16 && <= 32, a validity check on a load parameter
Sylpheed RE agent
2026-08-27 09:48:36 +00:00
be0f2b3124
re: [phase+10152]/[phase+10156] are an answer and a request state
Sylpheed RE agent
2026-08-27 09:39:52 +00:00
bcff20e4cb
isl: built-in 104 is request_next -- named from the game's own log string
Sylpheed RE agent
2026-08-27 09:31:01 +00:00
3fa898093f
isl: rename built-ins 8/9/93 to stopwatch_start/_elapsed/_stop
Sylpheed RE agent
2026-08-27 09:21:04 +00:00
11bcf283cb
re: the timer message's consumer is a runtime registry, not a tag compare
Sylpheed RE agent
2026-08-27 09:12:36 +00:00
a09c9e6517
re: timer_set's second argument is a SECOND countdown, not a warning threshold
Sylpheed RE agent
2026-08-27 09:03:18 +00:00
dde62c9afe
re: read_freg counts SECONDS -- the 32 "flags" are a stopwatch bank
Sylpheed RE agent
2026-08-27 08:48:49 +00:00
0033047768
re: read_freg reads the timeline's clock array -- "six clocks" was my mislabel
Sylpheed RE agent
2026-08-27 08:28:26 +00:00
eda1f3e368
re: A/B in the trigger test -- searched, not settled, and the matrix reading excluded
Sylpheed RE agent
2026-08-27 08:21:58 +00:00
70df1c3a1b
re: the kind-1 trigger condition is the same test with a pre-filter -- mechanism read end to end
Sylpheed RE agent
2026-08-27 08:14:24 +00:00
a3c8257c64
re: the kind-0 trigger condition is a point-to-segment proximity test
Sylpheed RE agent
2026-08-27 08:08:01 +00:00
d27bf54998
re: both trigger kinds watch a ROUTE -- the unit-reaches-route mechanism
Sylpheed RE agent
2026-08-27 08:00:22 +00:00
af9e8006b6
re: +24 is the trigger kind tag -- built-in 19 registers a routine, built-in 25 a route
Sylpheed RE agent
2026-08-27 07:53:26 +00:00
42544b4969
re: the unreached code -- five mechanisms eliminated, nothing in the file names it
Sylpheed RE agent
2026-08-27 07:46:56 +00:00
1c21a00f7c
re: two trigger appenders -- built-in 19's node carries the handler routine
Sylpheed RE agent
2026-08-27 07:38:24 +00:00
bee8d96394
re: decode the trigger node -- and withdraw two of my own claims about it
Sylpheed RE agent
2026-08-27 07:30:41 +00:00
62f52a4543
re: sub_822737C8 is the coroutine spawner; the record's third word is the MAIN ENTRY
Sylpheed RE agent
2026-08-27 07:22:51 +00:00
f37df54ed2
re: the timeline's consumer confirms the decode, and kind is a clock index
Sylpheed RE agent
2026-08-27 07:15:25 +00:00
c696657613
re: the trailing data table is a per-phase TIMELINE of scheduled routines
Sylpheed RE agent
2026-08-27 07:07:35 +00:00
7cd2370372
re: entry_a is a code/data boundary, not an entry -- and the decoder was reading data as code
Sylpheed RE agent
2026-08-27 06:59:58 +00:00
e897da3017
re: the 0x1883 record carries entry points -- every phase exit is now reachable
Sylpheed RE agent
2026-08-27 06:51:16 +00:00
6c9e2ca44d
re: the trigger-queue appender is built-in 25 -- the script appends, not the engine
Sylpheed RE agent
2026-08-27 06:42:47 +00:00
6cbfe0524f
re: the sufficient side -- each phase exit now names the condition that FIRES it
Sylpheed RE agent
2026-08-27 06:34:39 +00:00
6c892b5e25
re: read the three built-ins that appear inside clear conditions -- none named
Sylpheed RE agent
2026-08-27 06:27:00 +00:00
2876449965
re: phase-guards for all 28 stages, and a 6/6 cross-check from an unrelated method
Sylpheed RE agent
2026-08-27 06:19:44 +00:00
983c5d112c
re: the per-phase clear conditions, by dominance over the ISL CFG
Sylpheed RE agent
2026-08-27 06:12:41 +00:00
29eda81ede
re: recover ISL conditions by CFG dataflow instead of a linear walk
Sylpheed RE agent
2026-08-27 06:02:37 +00:00
b42cd7183c
re: builtin80 is a command -- and finding that exposed an 11.75% bug in my tracker
Sylpheed RE agent
2026-08-27 05:53:20 +00:00
8af97adbc5
re: derive UNIT_ARG from the implementations -- 31 built-ins take a unit, not 31 of 55
Sylpheed RE agent
2026-08-27 05:45:10 +00:00
4f37a4eb4c
re: fix the wrong ISL conditions -- the cause was a coroutine boundary, not the filter
Sylpheed RE agent
2026-08-27 05:36:02 +00:00
f32def9a05
re: resolve every ISL condition's comparand -- the clear conditions are readable
Sylpheed RE agent
2026-08-27 05:28:50 +00:00
0287a78633
re: close the ISL operand chain -- built-in result is special[0], via a vtable
Sylpheed RE agent
2026-08-27 05:21:10 +00:00
504a042698
re: read the ISL branch handlers -- it is a condition-code machine
Sylpheed RE agent
2026-08-27 05:10:50 +00:00
228680edf0
re: the ISL stream is flat -- refute the "needs coroutine entry points" blocker
Sylpheed RE agent
2026-08-27 05:00:49 +00:00
3e4dd3ca72
re: diff the legacy IDXD reader against the field table -- 17.54% wrong, with an exact predicate
Sylpheed RE agent
2026-08-27 04:52:05 +00:00
157c4558af
backlog: mark the freeze entry's "first step" done, and rule out --log_mask=0
Sylpheed RE agent
2026-08-27 04:43:18 +00:00
b9dab5772a
re: the mission scripts were already found -- correct a stale 🔴 that cost three iterations
Sylpheed RE agent
2026-08-27 04:22:25 +00:00
b3d146b758
re: the script lookup is a tag_hash directory search; pak route dead under both hashes
Sylpheed RE agent
2026-08-27 04:15:33 +00:00
6d6766db18
re: close the pak route properly (41 paks) and read the script loader's own code
Sylpheed RE agent
2026-08-27 04:09:18 +00:00
d9032af5be
re: refute the .embsec_ script candidate; narrow the pak route with 616 hash probes
Sylpheed RE agent
2026-08-27 04:01:34 +00:00
34329ad05c
re: THE DECREMENT IS MEASURED -- REMAINING OB is fully solved
Sylpheed RE agent
2026-08-27 03:53:08 +00:00
a25ddabb11
tools: add SYLPH_WEAKEST target scoring; record that assert_stage != in flight
Sylpheed RE agent
2026-08-27 03:27:35 +00:00
00dc0162aa
re: quantify why the OB kill test keeps failing -- attackers are damaged, not missed
Sylpheed RE agent
2026-08-27 03:07:33 +00:00
4a78b1bc86
re: turret control CONFIRMED, arrival timing n=3, decrement still unproven
Sylpheed RE agent
2026-08-27 02:42:46 +00:00
ad87f6e47d
re: kill run -- arrival timing reproduced (n=2), decrement inconclusive, "live attackers" refuted
Sylpheed RE agent
2026-08-27 02:18:29 +00:00
054bd0794c
re: CONFIRMED -- the A-route arrival times predict the OB counter's steps exactly
Sylpheed RE agent
2026-08-27 01:55:07 +00:00
0feadc4205
re: mission TIME is the liveness oracle, and it explains the earlier "0 movers"
Sylpheed RE agent
2026-08-27 01:34:09 +00:00
b88a23403e
re: test what the 'A' route kind means across all 28 stages -- enriched, not "attackers"
Sylpheed RE agent
2026-08-27 01:15:49 +00:00
bf5716373b
re: the 'A' route kind names the objective squadrons and predicts the whole OB trajectory
Sylpheed RE agent
2026-08-27 01:08:21 +00:00
027d6c8a17
re: phase-1's four attacker squadrons are measured -- all n=4, 16 craft
Sylpheed RE agent
2026-08-27 01:02:06 +00:00
1ed4d4b140
re: test the OB hypothesis's weak point statically -- it holds, but a premise was wrong
Sylpheed RE agent
2026-08-27 00:55:27 +00:00
b0b285d571
re: hypothesis for what REMAINING OB counts -- marked attackers, 4 per squadron
Sylpheed RE agent
2026-08-27 00:48:52 +00:00
b0081fd81a
re: refute the OB entity-flag on the FULL enumeration -- the stationary-entity hole is closed
Sylpheed RE agent
2026-08-27 00:40:53 +00:00
a22ef5f96f
re: LOCATE REMAINING OB at 0xbdb69668, and refine the ...9668 pattern
Sylpheed RE agent
2026-08-27 00:23:22 +00:00
2add603485
re: refute the "counter sits at page offset 0x9668" prediction
Sylpheed RE agent
2026-08-26 23:57:25 +00:00
c2b7c93792
re: correct my own OB write-up -- I refuted a stale status line, not an open question
Sylpheed RE agent
2026-08-26 23:57:01 +00:00
45a46fadea
re: REMAINING OB's address is run-dependent -- cross-run stability refuted
Sylpheed RE agent
2026-08-26 23:34:36 +00:00
c7d7df0ead
re: WITHDRAW "the absence is structural" -- capital ships do have +0x130 blocks
Sylpheed RE agent
2026-08-26 23:20:48 +00:00
b2206b46a6
re: the guarded route now verifies end-to-end, and the menu order is confirmed
Sylpheed RE agent
2026-08-26 23:08:11 +00:00
914ada4605
tools: never crop to a window too narrow to be a game frame
Sylpheed RE agent
2026-08-26 23:02:08 +00:00
f307c6f31b
tools: add assert_stage.py and a menu guard; record that the guard was not enough
Sylpheed RE agent
2026-08-26 22:56:22 +00:00
6aa31e52ba
tools: reject degenerate captures in screen_id instead of classifying them
Sylpheed RE agent
2026-08-26 22:55:58 +00:00
f2c54eeec2
re: pin the GHAD field base -- it is tag+4, not the tag+8 I guessed
Sylpheed RE agent
2026-08-26 22:39:02 +00:00
4ae63cb3d1
re: the stage drift is navigation, not the save -- slot 01 is deterministically Stage 02
Sylpheed RE agent
2026-08-26 22:32:30 +00:00
b99bd65745
re: the two enumerations are different structures; only the vtable scan is complete
Sylpheed RE agent
2026-08-26 22:24:35 +00:00
31b5c2bd9e
re: refute the projectile hypothesis; the count inflation is 2x duplication + arrivals
Sylpheed RE agent
2026-08-26 22:09:07 +00:00
df4b79bfd2
re: the live entity readout works end-to-end; "0 movers" was a state
Sylpheed RE agent
2026-08-26 21:54:23 +00:00
0256d71e78
re: refute my own position anchor, withdraw the entities2 "defect", find the trap
Sylpheed RE agent
2026-08-26 21:36:47 +00:00
a1e36df498
re: withdraw "the speed cannot be used", and close the world-unit item
Sylpheed RE agent
2026-08-26 21:19:22 +00:00
4673818c03
re: RESTORE "one world unit is one metre" -- the objection conflated two families
Sylpheed RE agent
2026-08-26 21:18:54 +00:00
ed2836777e
backlog: record what the world-unit measurement now actually needs
Sylpheed RE agent
2026-08-26 21:10:26 +00:00
1247d7a512
re: world-unit attempt -- control paired, HUD reached, two tool defects found
Sylpheed RE agent
2026-08-26 21:10:10 +00:00
Sylpheed RE agent