Probe mappin route event dispatch

2026-06-20 00:59:35 -05:00
parent 3b0a66a87a
commit 2bbc6cbb46
3 changed files with 411 additions and 4 deletions
@@ -26,6 +26,12 @@ Current behavior:
  `0x8d136c`, `0x431a34`, `0x55a4e4`, and `0x14de238`.
 - For those listener callbacks, logs the listener object, event pointer, common
  object fields, and vtable slots on candidate nested owner/service objects.
+- Hooks the route handoff found from the journal listener bridge:
+  `0x598250`, `0x13763d8`, `0xaa62d0`, `0xaa6330`, `0x27abd7c`, and
+  `0x5625a4`.
+- Logs mappin route-event fields, active/deactive route refs, the mappin
+  active-route map at `system + 0x1a0`, and the route observer list at
+  `system + 0x280`.
 - Resolves the native mappin system when one of those paths fires, logs relevant
  vtable slot addresses, and temporarily hooks the route-adjacent slots.

@@ -38,6 +44,11 @@ Current route-probe focus:
 - mappin-system slots `0x1f0`, `0x280`, and `0x2f0`
 - `JournalManager.TrackEntry` implementation: `0x5944fc`
 - non-default `TrackEntry` listener callbacks listed above
+- journal/mappin route bridge candidate: `0x598250`
+- mappin route-event enqueue: `0x13763d8`
+- mappin route-event handler: `0xaa62d0`
+- mappin route activate/deactivate: `0xaa6330`, `0x27abd7c`
+- route-build candidate called by the bridge: `0x5625a4`

 Quest/objective pins did not fire the mappin tracking hooks in live tests. The
 REDscript decompile shows that those pins call `JournalManager.TrackEntry`