Event calendar
The event calendar overlays recurring in-game cadences — including VS, Arms Race, Alliance Exercise, Zombie Siege and Storm — with your alliance's own schedules, train slots, announcements and treaty deadlines. Officers see clashes; members see the same week and can open the event that applies to them.
// ON THIS PAGE
What's on the calendar
// NOTE
The calendar pulls from every coordinated source the platform knows about and lays them on a single weekly grid:
- VS week — the six VS days (Mon construction, Tue building, Wed tech, Thu hero, Fri total mobilization, Sat donations) with the day's focus marked.
- Desert Storm — your configured DS day and time, plus the auto-created match for the week if one exists.
- Recurring alliance events — Ghost Ops, Alliance Exercise (Marshal's Guard), General's Trial and Zombie Siege occurrences resolved from the cadence and settings your alliance has enabled. Officer-triggered events use the next scheduled occurrence rather than pretending the game picked a fixed weekday. Manage them from Recurring Events.
- Arms Race phase boundaries — the six 4-hour phases per day, anchored to your server reset hour.
- Train slots — your conductor and VIP for each day from the auto-generated train schedule.
- Scheduled announcements — anything you have on a recurring or scheduled cadence.
- Treaty / NAP deadlines — days when an active NAP expires, surfaced for officer planning.
Reading the week
Each event type has a distinct colour. Days with overlapping events (DS day landing on an Alliance Exercise run, for example) stack the chips so you can see at a glance which days are busy. Click any chip to jump to that event's detail page — opening DS for that match, a Marshal's Guard ranking entry, and so on.
// NOTE
Common uses
- Sunday-night planning. Skim the upcoming week, spot the busy days, post the briefing in Discord.
- Avoiding announcement clashes. Don't schedule a non-urgent recruitment post for VS Day 5 — it gets buried under reshield reminders.
- Picking a NAP renewal date. Aim for a quiet day so the negotiation isn't squeezed by a cross-server event.