Evony Hive Layout Strategy: Place Every Keep with Purpose

Apr 19, 2026 by evonytools 6 min read

TL;DR: A hive is not just about clustering keeps together. Strategic placement based on role, defensive depth that buys time for shielding, and a teleport plan that members actually follow are what separate a defensible hive from a collection of keeps sitting next to each other.

Why hive layout matters

An alliance “hive” is when members teleport their keeps close together in a tight cluster on the world map. It is not a formal game mechanic — it is a player strategy that has become standard practice because it works.

A well-designed hive provides:

Defensive depth — attackers hit outer keeps first, giving inner keeps time to activate peace shields or ghost their troops
Rally support — when a rally is called, members in the hive can join instantly instead of marching across the map
Mutual reinforcement — keeps that are close together can reinforce each other with troops, strengthening defense for everyone
Psychological deterrence — a tight, organized hive signals to other alliances that your team is coordinated. Scattered keeps invite attacks.

A disorganized hive — keeps spread across 50+ tiles with no clear structure — tells every other alliance on the server that your leadership is not paying attention.

Inner ring, outer ring, and defensive layers

The standard hive uses a concentric layout:

Inner ring (core)

R5 keep at the center or near-center
R4 keeps surrounding the R5
Your highest-power members who can absorb hits and reinforce quickly
This ring should never have gaps — empty space in the inner ring is a defensive liability during SvS or kill events

Outer ring (perimeter)

Mid-power members and newer members
Arranged in a continuous formation around the inner ring
Outer ring members are the first line of defense during enemy attacks
They should be prepared to bubble (activate a peace shield) quickly if overwhelmed, and should have alliance chat monitored for defense calls

Buffer and approach zones

Think about where attacks are likely to come from. If a hostile alliance lives to the east, your eastern perimeter should be your strongest.

Place high-power, combat-ready members on the side facing threats
Place newer or lower-power members on the quieter side where attacks are less likely
Leave no keeps isolated outside the main cluster — a solo keep is a free kill during SvS

Role-based keep placement

Not every member needs the same position. Assign slots based on what each member does during events.

R5 (center):

Best-defended position, surrounded by R4s and high-power members
Shortest distance to reinforce any point in the hive
If the R5 gets zeroed (all troops killed), alliance morale takes a massive hit. Protect this keep.

R4s (inner ring, spread around the R5):

Each R4 covers a section of the hive for coordinating defense and reinforcement
If your R4s have different strengths (one focuses on ground troops, another on mounted), position them facing the direction threats are most likely to come from so their counter-strengths are in play

Rally leaders (outer ring, threat-facing side):

Rally leaders need to launch marches quickly. Position them on the edge facing likely targets or enemy territory.
Their troops are often out on rallies, so their keeps may be lightly defended — place them where allies can reinforce if needed.

Newer members / probation (outer ring, low-threat side):

Place new members on the side facing away from hostile alliances
They learn hive discipline in a lower-pressure position
If they forget to bubble during an attack, the impact on the core hive is minimal

Teleport coordination

The best hive layout is useless if members do not teleport to their assigned positions.

The assignment process:

Design the hive layout using a map or tool (screenshot with grid overlay, or a hive map maker)
Post the layout with each member’s name at their assigned position
Give members a 24-hour window to teleport to their assigned slot
After 24 hours, check compliance. Anyone not in position gets a direct message.
Before major events (SvS especially), re-verify everyone is in position

Teleport discipline:

Members should always have at least 2 random teleports in reserve
Targeted teleports are for precision positioning during active events — do not waste them on routine moves
If a member cannot afford teleports, the alliance should cover it from shared resources. A keep out of position weakens everyone.

For how teleport coordination fits into SvS preparation, see the sprint plan guide.

Keep-slot binding workflow

Once you have a hive design, you need a system for assigning members to specific positions. This is where most alliances get informal and pay for it later.

The binding workflow:

Design phase: R5 creates the hive layout with marked positions
Assignment phase: R4s assign members to positions based on role, power, and troop composition
Communication phase: post the assignments in Discord with each member tagged next to their position
Execution phase: members teleport within the designated window
Verification phase: R4 checks the world map and confirms everyone is in position
Maintenance phase: when members join or leave, update the layout and reassign positions

Alliance Studio’s hive map tool handles this with drag-and-drop keep placement and roster binding. If you are doing this manually, a screenshot with numbered positions and a spreadsheet mapping positions to member names is the minimum viable approach.

When to rebuild the hive

Hive layouts are not permanent. You should rebuild when:

Alliance size changes significantly (gained or lost 15+ members)
Power distribution shifts (a mid-power member became your strongest player through training or purchases)
Server politics change (new hostile alliance moved nearby, or a NAP broke and your previously safe side is now exposed)
Before major events (SvS especially) that require optimized positioning
After a hive break (enemy alliance punched through your perimeter during SvS and you need to close the gap)

Rebuild frequency: most alliances should review their hive layout monthly and do a full rebuild quarterly. More frequent rebuilds cause teleport fatigue and member frustration.

The rebuild process:

Export the current layout (screenshot or tool export) for reference
Design the new layout based on current roster, power distribution, and threat assessment
Communicate the changes with a clear timeline
Execute during a low-activity period (not the day before SvS starts)
Verify and adjust

Hive discipline during SvS

SvS is when your hive layout matters most. For 7 days, your server is under attack and your hive is your defensive formation.

SvS-specific hive rules:

Everyone teleports to their assigned position before SvS begins. No exceptions.
Members going offline must bubble up (activate a peace shield) or ghost their troops before logging off. An unshielded, unattended keep in the hive is a free target that also weakens the perimeter.
If the hive gets broken (enemy punches through), R5 calls a regroup at a predetermined backup location. Do not scatter randomly.
After regrouping, R4s do a headcount and reassign positions for the backup hive.

Ghosting within the hive context: Ghosting means sending your troops on long marches (to a distant resource tile or on a long-timer rally) so they are not in your keep if an enemy rally lands. During SvS off-hours, members who are sleeping or AFK should ghost their troops. A keep can get zeroed, but if the troops are out marching, they survive.

Common hive mistakes

Mistake 1: Random placement. “Just teleport near the hive” is not a strategy. Every keep should have an assigned position with a reason for being there.

Mistake 2: R5 on the outer ring. The R5 keep should never be on the perimeter. If the R5 gets rallied and zeroed, alliance morale tanks. Center position, always.

Mistake 3: Not accounting for troop composition. If all your ground-focused players are on the north side and the enemy attacks from the north with mounted troops, your defense is counter-picked. Spread troop types around the perimeter or stack the counter-type against the likely threat direction.

Mistake 4: Static layouts that go stale. A hive layout from 3 months ago does not reflect your current roster. Members join, leave, grow, and change roles. Review and update regularly.

Mistake 5: No teleport reserves. If your members do not have teleports, they cannot maintain the layout or reposition during emergencies. Include teleport reserves in your alliance resource planning.

For the full picture of how hive management fits into running an alliance, see how to run an Evony alliance. For the data management side of tracking keep assignments, see migrating from spreadsheets.