Clarify station overlay open note
This commit is contained in:
parent
1a8d69fab5
commit
08eb20cc17
1 changed files with 1 additions and 1 deletions
|
|
@ -77,7 +77,7 @@ anchor it, and where control is handed to neighboring subsystems.
|
|||
|
||||
- Station-detail overlay: the shell-side candidate preview pair now has a grounded world consumer too. `world_render_station_candidate_service_map_overlay` at `0x0043f640` reads the active `(station id, candidate id)` pair from `0x005ee4fc` and `0x005ee500`, scans the placed-structure collection, and then splits the legend by candidate mode. When the active candidate carries a nonzero route-style byte at `[candidate+0x46]`, the overlay uses the heavier helper `placed_structure_query_candidate_directional_route_overlay_summary` at `0x0047e690` in both directions between the preview station and each scanned site and formats the resulting directional rows as `3874` `Coming To %1` and `3875` `Going From %1`. When that byte is zero, the same overlay falls back to the direct local-service path through `placed_structure_query_candidate_local_service_metrics` and formats the two legend rows instead as `3876` `Current Supply @ < %1` and `3877` `Current Demand @ > %1`. Empty directional lanes collapse to `3878` `--None--`, and one title lane falls back to literal `All`. The nearby connection-state notes `3872` and `3873` are still tied to adjacent overlay-side ownership checks, but `3879` `Out of Sync` does not currently appear inside `0x0043f640` itself and remains a separate unresolved sibling owner.
|
||||
- Station-detail overlay, corrected boundary: `3879` `Out of Sync` is no longer an unresolved overlay sibling. It is now grounded under the multiplayer preview dataset path instead: `multiplayer_preview_dataset_service_launch_state_and_warn_out_of_sync` at `0x0046b780` checks global `0x006cd91c`, raises the `Out of Sync` shell status through `0x5386e0`, and then continues through the wider multiplayer preview launch-state service. So the station-detail overlay currently owns only the `Coming To`, `Going From`, `Current Supply`, `Current Demand`, `--None--`, and adjacent connection-state note lanes.
|
||||
- Station-detail overlay, ownership side: one reusable site helper is grounded now too. `placed_structure_query_linked_company_id` at `0x0047efe0` resolves the current placed structure's linked instance through `0x0062b26c` and returns its company id from `[instance+0x276]`; the overlay compares that id against the active company selector before deciding whether a scanned site should carry the `Already Connected by Another Company` note. The exact branch that emits `Out of Sync` is still unresolved.
|
||||
- Station-detail overlay, ownership side: one reusable site helper is grounded now too. `placed_structure_query_linked_company_id` at `0x0047efe0` resolves the current placed structure's linked instance through `0x0062b26c` and returns its company id from `[instance+0x276]`; the overlay compares that id against the active company selector before deciding whether a scanned site should carry the `Already Connected by Another Company` note. The remaining local gap on this branch is the exact branch that emits the neighboring `Not Connected` note.
|
||||
- Station-detail overlay, route-list side: the neighboring helper `placed_structure_append_unique_route_entry` at `0x0047f010` is now grounded as the append-if-missing builder for the six-byte route-entry list rooted at `[site+0x462]` and `[site+0x466]`. That matters here because the directional overlay query at `0x0047e690` consumes the same list, so the remaining uncertainty is no longer list ownership. It is down to the exact semantics of each entry's `u32` payload and the final `Out of Sync` chooser.
|
||||
|
||||
## Next Mapping Passes
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue