How to Run an Evony Alliance: The Complete R5 Playbook

Apr 14, 2026 by evonytools 7 min read

TL;DR: Running an Evony alliance is a leadership job, not a power contest. Set a weekly cadence, delegate to your R4s, enforce roster hygiene, and treat event prep as a non-negotiable rhythm. This guide covers everything from your first week as R5 to managing a full alliance without burning out.

The R5 job description nobody writes down

Being R5 is not about having the biggest keep or the best generals. It is about making decisions that your entire alliance depends on, often with incomplete information and usually at 2 AM before a battlefield event.

Your actual responsibilities break down into four buckets:

Roster management — who joins, who stays, who gets promoted, who needs to leave
Event coordination — BoC, BoG, SvS, rally calls, boss kills, and whatever seasonal events the game throws at you
Communication — keeping members informed without drowning them in pings
Diplomacy — NAPs, server politics, coalition management

If you are doing all four alone, you will burn out in three months. The first thing to learn is what to delegate.

The weekly cadence that keeps alliances alive

Most alliances that die do not implode from a single disaster. They decay from inconsistency. Members stop showing up because nothing is predictable. Fix this with a weekly cadence.

Daily beats:

Check Discord for new join requests or messages from R4s
Scan the roster for members who left the alliance or went offline unexpectedly
Respond to any pending alliance mail

Weekly beats:

Monday: review the roster for inactivity (anyone offline 7+ days gets a DM, 14+ days gets a conversation)
Tuesday: check BoG registration if it is open — make sure your Event R4 has selected the timeslot and the 20-member roster is locked
Wednesday: BoG day — confirm your team is online and ready before the match starts
Friday: check donation progress and alliance tech contributions
Saturday: BoC day — same drill as Wednesday. Timeslot selected, team picked, everyone briefed.
Sunday: R4 leadership meeting (15 minutes in voice, cover any issues, plan the next week)

Event-driven beats:

When SvS is announced: start the SvS preparation guide immediately — you have a full week of competition ahead
Post-event: run a quick after-action review (what worked, what broke, what to change)

This cadence does not require heroic effort. It requires consistency. Miss two weeks and your members notice. Miss four and they start shopping for other alliances.

What to delegate to your R4s

You should have 3-5 active R4s. Each one should own a specific domain:

Recruitment R4 — handles applications, vetting conversations, probation check-ins. See recruiting active members for the full pipeline.
Event R4 — manages BoC and BoG team selection, registers the alliance for battlefield events, picks timeslots from the available options, and selects the 20 participants. Owns the event calendar.
Rally R4 — leads or coordinates rallies during kill events and boss hunts. Needs to understand rally timing and coordination.
Diplomacy R4 — handles external communications, NAP negotiations, server coalitions.
Discord R4 — keeps the Discord organized, manages bot commands, handles moderation.

Not every alliance needs all five roles filled separately. In a smaller alliance, one R4 can cover events and rallies. The key principle: never have zero people covering a domain.

Give your R4s clear authority. “You can kick probation members without asking me.” “You can adjust the BoC team roster without waiting for my approval if I am offline.” The less they need to escalate, the faster your alliance moves.

Roster hygiene: who stays, who goes

Roster hygiene is the hardest part of the R5 job because it involves telling people things they do not want to hear.

The rules should be clear from day one:

Minimum activity threshold (e.g., log in at least 4 of 7 days per week)
Minimum event participation (e.g., be available for BoC or BoG at least twice per month)
Minimum donation threshold (varies by server stage and alliance tech needs)
Communication expectation (check Discord at least every 48 hours)

When someone falls below threshold, the process should be consistent:

Day 7 inactive: R4 sends a friendly DM. “Hey, noticed you’ve been quiet. Everything okay?”
Day 14 inactive: R5 or senior R4 sends a direct message. “We need to hear from you by [date] or we’ll need to free the slot.”
Day 21 inactive with no response: Remove from the alliance. No drama, no public announcement.

The goal is never punishment. It is maintaining a roster where every slot is held by someone who contributes. A smaller alliance with high activity is stronger than a full alliance where half the roster is dead weight.

For a detailed framework on handling inactivity, read managing inactive members.

Setting expectations at join time

Most roster problems start at recruitment. If you let someone join without explaining the rules, you cannot fairly enforce those rules later.

Every new member should receive:

Written rules — posted in a pinned Discord channel or alliance mail. Cover activity, donations, event participation, communication expectations.
Probation period — 14 days is standard. During probation, the member should demonstrate activity, fill at least one rally, and introduce themselves in Discord.
R4 point of contact — assign a specific R4 to check in with the new member at day 3, day 7, and day 14.
Clear promotion criteria — what does it take to go from R1 to R2? R2 to R3? Make it measurable.

When expectations are clear, enforcement is easy. When expectations are vague, every kick feels arbitrary and generates drama.

The event prep workflow

Events are where alliances either look organized or fall apart publicly. The key thing to understand is that Evony dictates when events happen — BoG is weekly (typically Wednesdays), BoC is weekly (typically Saturdays), SvS runs every two weeks for seven days. Your job as leadership is not to schedule events but to choose the right timeslot and pick the right team.

For BoC and BoG (20-member battlefield events):

When registration opens (24h before): R4 or R5 registers the alliance and selects a timeslot from the 9 available options. Pick one that works for your strongest 20 players.

12-24 hours out: select your 20 participants. Consider troop composition, general strength, and who is actually going to be online at that time. Have 3-5 alternates ready.

2 hours out: reminder ping to your 20. Confirm everyone knows their role and has their troops ready. Run through the BoC preparation checklist if applicable.

During the event: R5 calls strategy in voice. Keep comms focused. The match is 2 hours — pacing and building occupation matter more than raw kills.

After the event: run a 10-minute debrief. Three questions: what went well, what broke, what do we change for next time.

Alliance Studio automates the team selection and roster-check parts of this workflow, which removes the biggest time sink from event prep.

Diplomacy and NAPs basics

Server politics matter more than most R5s realize when they first take the role.

Non-Aggression Pacts (NAPs):

Always get NAPs in writing (Discord DMs are fine, but screenshot them)
Be specific: “NAP covers KE hits and tile stealing. Does not cover SvS.”
Review NAPs quarterly. Servers shift, alliances merge, and yesterday’s ally might be tomorrow’s problem.

Coalition management:

Join a coalition if your server has them, but do not sacrifice your alliance’s interests for coalition politics
Attend coalition leadership meetings (or send your diplomacy R4)
Share intelligence, but be selective about what you reveal about your own alliance’s strength

When NAPs break:

Document the incident with screenshots
Contact the other R5 directly before escalating to coalition leadership
If the break was minor (one member acting alone), work it out privately
If the break was deliberate, plan your response before acting emotionally

Red flags that kill alliances

After watching dozens of alliances collapse, the warning signs are consistent:

R5 burnout — the leader stops logging in daily, stops responding to DMs, delegates nothing. The alliance drifts.
R4 power struggles — two R4s competing for influence instead of collaborating. Fix this immediately by clarifying domains.
Inactive roster bloat — 30% of the roster has not logged in for a week, and nobody is enforcing standards.
Event apathy — you cannot fill your BoC or BoG roster with 20 willing players. This means either the team selection process is broken or your members have checked out.
Communication vacuum — the Discord is dead. No announcements for a week. Members assume the alliance is dying and start leaving.
Drama tolerance — toxic members are kept because they have high power. This always poisons the culture eventually.

If you spot three or more of these simultaneously, your alliance is in trouble. The fix is almost always the same: recommit to the weekly cadence, enforce roster standards, and communicate openly about what is changing.

Building for the long term

The best alliances are not the strongest on the server. They are the most consistent. Members stay because they know what to expect, they trust the leadership, and they feel like their time is respected.

That means:

Prepare for game events on a predictable rhythm
Enforce rules consistently (no exceptions for high-power members)
Communicate changes before they happen
Recognize contributions publicly (leaderboards, shoutouts, role promotions)
Ask for feedback and actually act on it

Running an alliance is a real leadership skill. The patterns you learn here — delegation, communication, accountability, conflict resolution — transfer directly to managing teams in other contexts.

If you are still managing your roster with spreadsheets and Discord DMs, consider whether a dedicated tool might save you hours per week. The workflow patterns in this guide are exactly what Alliance Studio was built to support.