Use this when your attention is needed now. This page is the same flow the team uses when a player is frustrated, a map embed is flaky, or performance is spiking during peak hours.
1 First-response stack (single page checklist)
Ask for platform, exact edition, edition suffix (.Name for Bedrock commands), server/region, and if they can reproduce in a second attempt.
Send them map.aowmc.com open in a new tab. If map doesn’t render, switch to backup host and compare with /deaths.
Grab their exact command output or behavior timeline in /deaths + server chat references before changing anything.
2 Emergency map playbook
This is what we use when map tiles won’t render or coordinates are out of sync.
Use map.aowmc.com if the main map endpoint stalls more than 15 seconds. Keep this as a temporary path only.
1) Map check 2) /deaths 3) /backtrack 4) check known waypoints 5) if needed, call staff to secure base coordinates.
If the browser caches stale tiles, use private tab or another browser before you escalate. Check if HTTPS load blocks are shown in browser privacy settings.
3 Crossplay and claim support flow
| Symptom | First check | Action | Escalation |
|---|---|---|---|
| Bedrock player shows dot mismatch | Command target includes .? |
Ask for command with example /msg .Player hi |
Tell player to check display settings if still mismatched |
| Cannot open commands in private messages | Crossplay prefix and permissions | Have them try a simple command first: /list or /spawn |
Check staff command permission overrides |
| Claim access denied | Check name in command | Have them confirm /trust and /containertrust |
Inspect claim owner and trust list if still denied |
| Player says “frozen sky” | Known Bedrock client presentation issue | Use /realtime, scoreboard, /top as time source |
Escalate only if mob logic also appears broken |
4 Routine server checks during active sessions
5 Backup and incident handoff
Keep this simple and predictable. A good handoff beats a perfect command.