This page is your map-first incident playbook. Keep it tight when players are confused, disoriented, or losing gear.
Primary: map.aowmc.com
Fallback: map.aowmc.com
Recovery commands:/deaths + /backtrack
Goal: clear route + coordinate confidence
1 Triage sequence (first 30 seconds)
Check routeOpen the map in a new tab directly at
map.aowmc.com so private-page iframe state is eliminated.Confirm hostTry the fallback host if the primary stays dark for longer than 12 seconds.
Check auth stateAsk the player what client, platform, and what they see in chat when loading map markers.
Confirm recovery modeUse
/deaths and /backtrack before assuming map data is incorrect.2 Symptom-to-fix matrix
| Symptom | Most likely cause | Exact fix |
|---|---|---|
| Dark tiles / gray world | Render pipeline delayed | Hard refresh map tab, then wait 10–15 seconds. |
| Map loads but no players | Tile rendering vs player visibility lag | Ask player to move, then rejoin and re-open map in full-screen. |
| Wrong location marker | Pan/zoom confusion | Reset with world center and use spawn as reference. |
| Iframe-only failures | Privacy or frame-blocking rules | Switch to direct URL, keep the same browser session. |
3 Recovery command chain
/deaths
/backtrack
/home home
/wp
When to escalate: after two minutes of failed map recovery and commands still not showing a route, escalate in staff channels with the last map URL used and command timestamps.
4 Map etiquette and safety while recovering
Don’t crowd
Do not build or route-check while recovering another player’s grave; avoid confusion.
Coordinate first
Share exact recovery commands and route sequence with a helper.
Use backup host
Primary map + fallback host gives two independent checks in one support window.
Record time
Include time, player count, platform, and browser context in handoff notes.
Report anomalies
If recovery fails twice, tag operations and attach timestamps and map links.
Close when safe
Once base and route are confirmed, close the issue or continue to a command routine.