Open map.aowmc.com in a fresh browser tab first to validate endpoint health before using the embedded map.
1 Open and stabilize fast
When every second matters, use this sequence so players can get their bearings in seconds.
If rendering appears stuck, retry map.aowmc.com immediately. Use this only while primary recovers.
The embedded map disables controls by default. Enable controls only during active scouting, then leave the map region to auto-lock.
2 Endpoint matrix
Use this quickly from support channels and Discord announcements.
| Endpoint | Purpose | Preferred action | Use case |
|---|---|---|---|
map.aowmc.com |
Primary public map | Use for normal map checks | Daily scouting and planning |
map.aowmc.com |
Direct render fallback | Try when primary is delayed | Quick incident fallback |
3 Scouting and recovery loops
A map-safe play path for long trips and disorientation incidents.
Open map + note route direction + destination. Confirm roads, biomes, and water paths before committing a long run.
Command pair:/spawn, /map (if available)
Compare death point, last-known landmarks, and map history. Use the map + /backtrack when possible.
/deaths, /backtrack
Before ending a session, log dangerous routes and failed waypoints for quicker recovery support next time.
Support note: share coords and a link-safe world name.4 Embedded map failure modes
If players report blank maps or stale tiles, use this checklist in order.
Open map in a new tab first, then return to the embed. This clears stale iframe state in many cases.
Use fresh private tabs for map links. Some browsers block mixed mixed-frame requests after long inactivity.
Wait for a cache cycle and then reload the map path. On sustained issues, verify both endpoints and compare behavior.
Keep map controls disabled on pages. When controls lock unexpectedly, tap the map button to re-enable and try one direction at a time.
5 Reference flows
Use these links for support handoffs and live playbooks.