1 Keep it stable during long sessions
Map exploration and long flights can load pressure into fresh chunks. If lag spikes, slow pace, map zoom down, and avoid repeated teleports into unchecked biomes.
Heavy mob concentrations should feel dangerous, not breaking. If a base feels rough, move up, build clean pathways, and let redstone lag counters settle.
Bedrock and Java run through a translation layer. If commands lag but world motion is okay, verify connection quality before opening support.
2 Player-side check list
Lower render distance in hard sessions, disable FSR/low-FPS overlays, and stay off unstable public proxies.
Use a wired or stable Wi-Fi profile. Keep client graphics steady and test another world first if your HUD feels stale.
Prefer join after server startup windows and restart announcements to minimize race conditions.
3 Incident playbook
- Soft check: verify DNS/route by opening
map.aowmc.comand checking status. - Device check: restart client, rejoin with a clean cache, and test another network if possible.
- Server check: check
/realtime, /pingbehavior, then try /spawn, /home. - Data check: if claims/shops were involved, capture exact location and commands from
/log. - Escalate: include timestamp, platform, and action steps in support with a map link.
4 Maintenance and backups
Service is managed by systemd, with automatic restart on process failure and monitored service timing.
World and plugin state are backed up frequently. Admins recover from backups first for non-critical incidents before manual restoration.
Live map runs on the same data pipeline; if map misses updates, clear cache and retry directly at map.aowmc.com.
In-house plugins are loaded modularly. If a subsystem misbehaves, staff can disable one feature without taking down the entire stack.