Rule out early post-load setup owners
This commit is contained in:
parent
499462fae5
commit
25a97d209f
3 changed files with 18 additions and 0 deletions
|
|
@ -1581,6 +1581,13 @@ Working rule:
|
|||
chase this `0x004384d0` handoff family directly instead of treating the remaining
|
||||
`[region+0x2a4]` / `[region+0x310/+0x338/+0x360]` gap as a generic continuation below
|
||||
`0x00444887`.
|
||||
- The early `0x004384d0` setup strip is tighter now too: before the conditional `320/321` gates it
|
||||
always runs `0x0044fb70` transport/pricing-grid setup and `0x0041ea50`
|
||||
candidate-local-service setup, and the extra arg-guarded `0x00421b60 -> 0x004882e0`
|
||||
default-region pair sits beside them as the last pre-`320/321` setup branch. Those helpers are
|
||||
already grounded as world-grid, candidate-table, and border-refresh owners rather than the
|
||||
missing `[region+0x2a4]` / `[region+0x310/+0x338/+0x360]` republisher, so they drop out of the
|
||||
remaining region-handoff search too.
|
||||
- The `319` lane is the strongest bridge inside that family: `0x004133b0` drains queued
|
||||
placed-structure ids through `0x0040e450`, sweeps every live site through `0x0040ee10`, and then
|
||||
reaches the already-grounded linked-site follow-on `0x00480710`. The `320` and `321` lanes are
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue