How it works

MTR Map Overlay reads MTR network data and renders it in the fullscreen map integrations. Its map cache is separated by dimension.

MTR server snapshot ─┐
                     ├─> dimension map cache ─> Xaero World Map renderer
MTR nearby client data┘                      └─> JourneyMap renderer

When the mod is installed on both client and server, the client probes dimension content hashes and requests changed snapshots. The server collects tracks, routes and landmarks; payloads are chunked, checked and assembled on the client. When the server does not support snapshots, the client cache falls back to nearby data already available from MTR.

Both maps use shared sampled rail geometry. Route colours become parallel bands on shared rails. The renderers cull tracks outside the current viewport, and JourneyMap keeps its layer aligned to the map’s pan and zoom. Xaero and JourneyMap are optional integrations; missing map mods are skipped.