Evony BoC Preparation Checklist: From Registration to Match Day

Apr 15, 2026 by evonytools 6 min read

TL;DR: BoC is a 2-hour match between two alliances, 20 members each, on a special battlefield map. The alliances that win do not just bring the strongest players — they pick the right timeslot, select a balanced team, assign roles around building occupation, and drill their supply carriage strategy. This guide walks through the full preparation process.

How BoC actually works

Battle of Constantinople is a weekly PvP event, typically held on Saturdays. Two alliances are matched against each other, and each side fields a team of 20 selected members on a dedicated battlefield map.

Scoring mechanics:

Building occupation is the primary point source. Constantinople itself awards 80 points per minute of occupation. Knight’s Halls award 32 points per minute each.
Troop kills contribute to your score — every enemy troop killed adds points.
Supply carriages appear on the map during the match. Controlling them adds resources and scoring opportunities. There are no boss monsters in BoC (that is BoG).

The match lasts 2 hours. The alliance with more points at the end wins.

Key distinction from BoG: Battle of Gaugamela (weekly, typically Wednesdays) uses the same 20v20 format but includes boss monsters like the Phoenix on the battlefield. BoC replaces bosses with supply carriages and weights building occupation more heavily. If you are preparing for BoG, the team selection process below still applies, but your in-match strategy needs to account for boss monster kills.

The registration window

Registration for BoC opens approximately 24 hours before the match. During this window, R4 or R5 must:

Register the alliance for the event
Select a timeslot from the 9 available options
Select the 20 participants who will fight on the battlefield

This is a leadership decision, not a democratic vote. The R4/R5 registering the event should already know which 20 players are available and strongest for the selected timeslot.

Timeslot selection tips:

Pick the slot where your strongest 20 members can all be online
If your alliance spans multiple timezones, maintain a spreadsheet or roster tool showing each member’s availability windows
Avoid selecting a timeslot just because it is convenient for leadership — your best tank might be in a different timezone than your R5

Building your BoC team of 20

Not all 20 slots are equal. You need specific roles filled.

Core roles:

Building capturers (6-8 players): fast marches, strong enough to take and hold Constantinople and the Knight’s Halls. These players need mounted or ground generals with strong attack stats and march speed buffs.
Defenders/reinforcers (4-6 players): once your team captures a building, these players reinforce and hold it. They need high troop counts and defensive generals.
Kill team (4-6 players): their job is to rally enemy keeps and eliminate troops on the field. Strong PvP generals and T12+ troops.
Carriage runners (2-3 players): fast marches to grab supply carriages before the enemy. March speed is more important than raw power for this role.

Selection criteria:

Troop tier and count matter more than raw power. A player with 2B power but low troop count is less useful than a 1B player with full T13 marches.
General quality for the assigned role. Your building capturer needs a fast, strong attack general — not their gathering general.
Reliability. Pick members who show up on time and follow calls. A no-show costs your team a slot they cannot replace.

Pre-match preparation (12-24 hours out)

Once your team of 20 is selected, the real prep begins.

Communicate the plan:

Post the team roster in Discord. Tag each member.
Assign roles: “You are on building capture. You are on defense. You are on the kill team.”
Share the opening strategy: “At match start, capturers rush Constantinople. Defenders follow 30 seconds behind. Kill team waits for the enemy’s first move.”

Individual preparation each member should complete:

Generals assigned to the right march presets (PvP general, not their gathering general)
Troops healed and ready (no wounded sitting in hospitals)
Buffs activated or ready to activate at match start (attack/defense/HP buffs from items)
March presets saved for their assigned role
Peace shield plan — members NOT on the BoC team should bubble up during the event window to avoid being hit while the alliance’s best fighters are on the battlefield

R4/R5 preparation:

Confirm all 20 members have acknowledged their role
Identify 3-5 alternates in case of last-minute dropouts
Review the opponent (if visible) — check their power, recent BoC results, known strategies
Set up the Discord voice channel and confirm it works

Match-day execution

T-30 minutes before match:

All 20 team members online and in Discord voice
R5 gives the final brief: opening moves, building priorities, when to rally vs. when to reinforce
Confirm alternates are standing by

T-10 minutes:

Everyone enters the battlefield staging area in-game
Final gear and general checks
Voice channel goes to “comms discipline” — only callouts and R5 instructions

During the 2-hour match:

The first 10 minutes decide most BoC matches. Whoever captures Constantinople first builds a massive point lead.

Phase 1 (0-10 min): Rush Constantinople and Knight’s Halls. Speed wins here. Building capturers go first, defenders follow.
Phase 2 (10-30 min): Consolidate holdings. Reinforce captured buildings. Kill team starts engaging enemy forces trying to retake buildings.
Phase 3 (30-90 min): Sustained occupation. This is the grind. Rotate defenders to keep fresh troops on buildings. Kill team picks off enemy rallies and weakened players.
Phase 4 (90-120 min): Protect the lead or make a final push. If ahead, play conservative — hold buildings and avoid risky fights. If behind, coordinate an all-in push on Constantinople for the point swing.

Communication during the match:

R5 calls building targets and priority shifts
One person monitors the scoreboard and calls out point gaps
Kill team leader calls rally targets
Everyone else executes and stays off comms unless reporting something critical

Supply carriage strategy

Supply carriages spawn at intervals during the BoC match. They are easy to overlook but can swing close matches.

Assign 2-3 fast players specifically to carriage duty
Carriages follow set routes on the map — learn them from previous matches
Grabbing a carriage before the enemy denies them resources AND gives you a scoring bonus
Do not pull your building defenders off to chase carriages. That is how you lose Constantinople.

After-action review

Within 24 hours of the match, run a short review. This can be a Discord thread or a 10-minute voice session.

What went well? Name specifics. “We captured Constantinople in under 2 minutes.” “Kill team eliminated their top player three times.”
What broke? Be specific. “We lost Knight’s Hall B because nobody reinforced after the first capture.” “Two members had the wrong generals equipped.”
What do we change? One or two concrete actions. “Add a dedicated Knight’s Hall defender.” “Run a general-check at T-60 instead of T-10.”

Track these reviews over time. After 3-4 BoC events, patterns emerge. Maybe you always lose the same building. Maybe your carriage runners are too slow. These patterns tell you where to invest your prep time.

The BoC prep template

Here is the complete timeline you can copy into your Discord:

BoC Preparation Timeline

Registration opens: Select timeslot + pick 20 members
T-24h: Post team roster + role assignments
T-12h: Confirm all 20 members are available
T-6h:  Alternates on standby for any dropouts
T-2h:  Individual prep checklist (generals, troops, buffs)
T-30m: All 20 in voice, final brief from R5
T-10m: Enter battlefield, comms discipline
T-0:   Match starts -- execute the plan

Post-match: After-action review (within 24h)

Adapt the timing to your alliance’s rhythm, but do not skip steps. Each checkpoint exists because something goes wrong when you skip it.

For how BoC prep fits into the broader picture of running an alliance, see the complete R5 playbook.