Tighten event condition target scope mapping

This commit is contained in:
Jan Petykiewicz 2026-04-06 01:11:06 -07:00
commit c1010458f8
9 changed files with 757 additions and 17 deletions

37
docs/atlas/multiplayer.md Normal file
View file

@ -0,0 +1,37 @@
# Multiplayer
Primary atlas source:
- [control-loop-atlas.md#multiplayer-session-and-transport-flow](/home/jan/projects/rrt/docs/control-loop-atlas.md#multiplayer-session-and-transport-flow)
Current grounded owners:
- `multiplayer_window_init_globals`
- `multiplayer_window_service_loop`
- `multiplayer_register_session_event_callbacks`
- `multiplayer_dispatch_requested_action`
- `multiplayer_preview_dataset_service_frame`
- `multiplayer_transport_service_frame`
- `multiplayer_transport_service_worker_once`
- `multiplayer_transport_service_route_callback_tables`
- `multiplayer_transport_service_status_and_live_routes`
Current bounded state blocks:
- session globals at `0x006d40d0`
- active session-event transport at `0x006cd970`
- preview dataset at `0x006cd8d8`
- Multiplayer window backing block at `0x006d1270`
- selector-view store rooted at `[transport+0xab4]`
What this note is for:
- Multiplayer window and preview-dataset ownership
- Session-event transport routing
- GameSpy-facing callback and live-route semantics
- Selector-view refresh, retry, and probe state
Highest-value open edge:
- The remaining owner-side callback roles behind the validated GameSpy packet branches and the
exact user-facing meaning of the selector-view sample or companion fields.