Reframe Tier2 source family frontier

This commit is contained in:
Jan Petykiewicz 2026-04-19 14:50:33 -07:00
commit 1dcb3bd51f
3 changed files with 38 additions and 0 deletions

View file

@ -57,6 +57,14 @@
`aux_candidate_collection_rebank_or_clone_records_by_availability_pass_and_refresh_owner_links`
`0x00419230` before the later world-load side continues, with destructor
`aux_candidate_collection_release_templates_queues_and_indexed_storage` `0x00419680`. The fixed
stock source-family layer above that clone pass is bounded now too: `0x004197e0` formats source
names from the `0x005f3c6c` / `0x005f3c80` style tables, routes them through parser
`0x00414490`, and only then falls into the same `0x00419230` rebank-or-clone sweep. The
recovered source-name table is `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`,
`Maintenance`, `ClpBrd`, `Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the
remaining Tier-2 load-side question is the style-family row-selection path into that later bank
pass rather than another hidden naming stage.
The fixed
tail is explicit now too: `0x00444dd0` writes one direct dword from
`[world+0x19]`, one zeroed `0x1f4`-byte slab under `0x32cf`, closes the package, derives the
preview path through `0x00442740`, and then conditionally emits the companion-image and

View file

@ -1282,6 +1282,13 @@
stay in `named_binding_comparison.binding_only_canonical_stems`. So the numbered Tier-2
families no longer belong under stock `BuildingTypes/*.bty` discovery either; they belong under
the scenario/live candidate-table projection seam above the now-grounded bare-name remap.
The stock source-family loader above that remap is bounded now too. `0x004197e0` builds source
names from the table at `0x005f3c6c` plus companion path table `0x005f3c80`, feeds each result
into `0x00414490`, and only then tails into `0x00419230`. The currently recovered source-name
set is `StationSml`, `StationMed`, `StationLrg`, `ServiceTower`, `Maintenance`, `ClpBrd`,
`Kyoto`, `Persian`, `SoWest`, `Tudor`, and `Victorian`, so the remaining Tier-2 source frontier
is the style-family row-selection path into the later banked clone pass, not another hidden
name generator.
The direct `+0xba/+0xbb` writer census now rules out a broad false lead too. The obvious new
stores at `0x004ecd42/0x004ecdaa` and `0x004ed5d5/0x004ed625` are only shell-side
portrait/string refresh helpers over a different id-keyed collection rooted through