Narrow tier2 kind-8 setup gate role
This commit is contained in:
parent
cfeb3e893c
commit
d583020b5b
2 changed files with 17 additions and 1 deletions
|
|
@ -138,6 +138,17 @@ So the bridge is now narrower and more concrete:
|
|||
- setup payload `+0x3b2/+0x3ba -> [profile+0x79/+0x7b]` are still only grounded on the setup-side
|
||||
panel and scroll-threshold path, not yet on the later Tier 2 rebuild owners
|
||||
|
||||
The `+0x20` side is tighter in a second way too. Current grounded downstream consumers of the
|
||||
mirrored world byte `[world+0x66de]` are mostly:
|
||||
|
||||
- the editor metadata checkbox or campaign-scenario flag path
|
||||
- the campaign-gated branches inside
|
||||
`0x00442c30 shell_apply_scenario_name_specific_post_load_world_and_object_fixups`
|
||||
|
||||
The currently grounded Tier 2 relevance of `+0x20` therefore reads more like a branch gate on the
|
||||
selected-year/reactivation path inside `0x00436d10 / 0x00443a50`, not like a later direct input to
|
||||
`0x00435630 / 0x00412bd0 / 0x00412c10` through the ordinary `[world+0x66de]` consumer set.
|
||||
|
||||
That means the next upstream question is now smaller than before:
|
||||
|
||||
- whether `Louisiana.gmp`'s unique `+0x14/+0x20` setup-core pair is enough to explain its coupled
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue