Recurring events
Recurring events let officers define a repeating event once — weekly, every N days, or a single date — and have it land on everyone's event calendar automatically. Start from a template or build your own cadence. A Pro feature, managed by R5/R4.
What it is
Most alliances run the same events week after week — bear traps, fortress battles, guild fights on a fixed rhythm. Rather than post each one by hand, an officer defines it once as a recurring event and it appears on the shared event calendar on its own cadence, for the whole alliance to see.
You can start from a template — the create screen offers a gallery of common events — or start blank with a custom event and set every field yourself. Each event carries a name, an optional description shown on the calendar entry, a schedule, and a set of reminder lead times.
Automatic translations
Choose the language used for the event name and description when you create or edit it. Members of a Pro alliance see that copy translated into their selected language on the event list, event detail and shared calendar.
Setting the cadence
Every event uses one of three cadences, plus a time of day in your alliance's time zone:
- Weekly — pick one or more days of the week (Mon–Sun). The event repeats on those days indefinitely.
- Interval — every N days from a start date, anywhere from 1 to 365. Good for events on a rhythm that doesn't line up with the calendar week.
- Once — a single date. A one-off that still benefits from sitting on the shared calendar.
// NOTE
Reminders
When you create or edit an event you can select reminder lead times — 15 minutes, 30 minutes, 1 hour, 2 hours, or a day before. These are saved alongside the event.
// TIP
Access and limits
Recurring events are a Pro feature managed by officers (R5/R4). Members below R4 don't see the management screen, and on the Free plan the surface shows what Pro unlocks with an upgrade prompt rather than the editor.
An alliance can keep up to 25 recurring events at once. Once you hit the cap, delete one to add another.
// TIP