EvonyTools Blog

Evony SvS Preparation Guide: A 10-Day Battle Plan

by evonytools 8 min read
svs events strategy checklist

TL;DR: SvS runs for 7 full days every two weeks. Your entire server competes, and points come from troop kills, temple occupation, throne capture, monster kills, Fire Spirits, and Ares Statues. This guide breaks down the 3-day prep window plus the 7-day event so your alliance enters prepared and sustains performance through the final day.

What SvS actually is

Server vs Server is the biggest recurring event in Evony. Every two weeks, your server faces off against another server. Unlike BoC or BoG where only 20 members fight on a special map, SvS involves your entire server — every alliance, every player.

How scoring works:

  • Troop kills — PvP kills on enemy keeps, marches, and tiles. The bread and butter of SvS scoring.
  • Temple occupation — temples on the world map generate points while held. Controlling temples is a sustained point source, not a one-time capture.
  • Throne capture — the ultimate objective. If your server captures and holds the enemy throne for 5 hours, you steal 50% of the enemy server’s total score. This is the single largest scoring swing in the event.
  • Monster kills — world map boss kills contribute to your server’s score. Fire Spirits and Ares Statues are special SvS-specific targets.
  • Server Monarch Competition — a 6-stage competition that runs alongside SvS with its own scoring mechanics.

SvS lasts 7 days. Not 3, not 4 — a full week. Alliances that plan for a short event run out of resources and motivation by day 4.

The 3-day prep window (Days 1-3)

Start preparing the moment SvS is announced. You have roughly 3 days before it begins.

Day 1: Assessment and communication

  • Announce SvS dates and the daily schedule to the entire alliance
  • Post a roster snapshot — who is available for the full 7 days, who has partial availability, who will be traveling or otherwise offline?
  • Assign SvS roles: rally leaders, temple defense coordinators, resource donors, scouts, and throne strike team members
  • Review your current resource stockpile (food, wood, stone, iron, gold, speedups)

Day 2: Build-up begins

  • Set daily troop training targets for each member based on their keep level and troop tier
  • Establish donation and resource pooling expectations — who donates what, and when
  • Review the hive layout and confirm everyone knows their assigned position
  • Coordinate with other alliances on your server. SvS is a server-wide effort. Establish communication with allied alliances for temple control and throne attempts.

Day 3: Final preparation

This is your last prep day. Everything should be finalized.

Checklist:

  • All members have met troop training quotas (or are close)
  • Resource donations are collected and distributed to rally leaders
  • Rally leaders have their generals assigned, leveled, and equipped
  • Hive positions are confirmed — every member knows their slot
  • Teleport reserves checked (minimum 2 random, 1 targeted per member)
  • Discord voice channels set up for SvS coordination (separate channels for rally calls, temple defense, general comms)
  • Shift leaders assigned for each timezone (SvS runs 24/7 for 7 days — you need coverage)
  • Emergency protocols communicated (what to do if your keep gets rallied while offline, when to bubble, when to ghost troops)
  • Peace shield strategy decided — which members bubble up vs. which stay exposed for quick rally response

Days 4-10: The 7-day event

Daily SvS routine

Every day of SvS should follow the same basic rhythm:

Morning briefing (10 minutes): R5 or shift lead posts the day’s objectives. “Day 3 of SvS. We’re ahead by 200M points. Focus on temple occupation today. Rally targets posted in the rally channel. Defensive stance after 14:00 UTC — bubble if you are going offline.”

Rally windows (2-3 per day): Schedule coordinated rally windows where your strongest players are online together. Outside these windows, members farm points individually through troop training, research, and monster hunting.

Temple rotation: Assign shifts for temple occupation. Temples generate points per minute of control, so maintaining a presence is critical. Coordinate with allied alliances to avoid wasting troops fighting each other for the same temple.

Throne attempts: A throne capture that holds for 5 hours steals 50% of the enemy’s total score. This is the game-changer. Throne attempts should be server-wide coordinated events with your strongest alliances pushing together. Do not attempt this alone or without a plan — a failed throne attempt wastes resources and gives the enemy free kills.

Evening handoff: If your alliance spans timezones, the outgoing shift lead briefs the incoming shift lead. “We ran 4 rallies today, 3 successful. Hospitals at 60% capacity. Temples A and C are held. Focus on defense tonight.”

Point strategy across 7 days

SvS points come from multiple activities. Do not over-commit to any single category:

  • Troop kills — highest risk, highest reward. Rally leads and their fill teams handle this.
  • Temple occupation — sustained passive income. Requires bodies on the ground but less direct combat.
  • Monster kills — Fire Spirits and Ares Statues are SvS-specific point sources. Assign teams to hunt these specifically.
  • Troop training — safe points that every member can earn. Set daily training targets.
  • Research and building — also safe points. Time your upgrades to complete during SvS.

Do not burn out on day 1. Some alliances go all-in on troop kills on day 1, exhaust their healing speedups, and then cannot fight for the remaining 6 days. Pace your combat activity so you can sustain pressure across the full week.

Troop composition and healing

Pre-SvS troop checklist

Every member should confirm they have:

  • Full march of their primary troop type (T12 minimum for competitive servers, T13/T14 if available)
  • At least 50% of a second march as backup
  • Hospital capacity to heal their full primary march at least twice over
  • Healing speedups to cover at least 5 days of combat (not 3 — you need the full 7 days)
  • Training speedups to rebuild losses overnight

For rally leaders:

  • Full top-tier march in their primary troop type
  • Backup march in a secondary type for counter-picks
  • March presets saved for common scenarios: PvP rally, boss rally, temple defense

Healing is where SvS is won or lost

The math is simple: if you cannot heal your troops, you cannot fight. And SvS lasts 7 days.

Pre-SvS healing audit:

  1. Each member reports their hospital capacity and current speedup reserves
  2. R4 aggregates the numbers. Total healing capacity should sustain 7 days of combat at your expected intensity.
  3. If the total is too low, spend the remaining prep days farming speedups and upgrading hospitals.

During SvS:

  • Heal immediately after every engagement. Do not let wounded troops pile up in hospitals.
  • Prioritize healing your highest-tier troops first (T14 > T13 > T12 and so on).
  • If healing reserves run low mid-event, switch to non-combat point activities (training, research, gathering) until reserves recover.

Emergency healing protocol:

  • Designate a “healing reserve” — 20% of total speedups reserved for the final 2 days.
  • If someone runs out of healing mid-event, the alliance pool covers them if you maintain shared resources.

Teleport plans and hive defense

Your hive layout is your defensive formation during SvS. Every member needs to know their position and have teleports ready.

SvS teleport rules:

  • Everyone teleports to their assigned hive position at event start
  • Minimum reserve: 2 random + 1 targeted teleport per member
  • Targeted teleports are for emergency repositioning during active attacks
  • Random teleports handle initial positioning and post-attack recovery

When the hive gets hit:

  • If an enemy alliance breaks through your perimeter, R5 calls a regroup location
  • Members teleport to the backup hive location (predetermined and communicated on day 3)
  • Do not scatter randomly. A scattered alliance loses the defensive advantage of the hive and becomes easy to pick off one by one.
  • After regrouping, assess damage and decide whether to reinforce the original position or hold the backup location.

Ghosting protocol: When offline or under heavy attack, members should ghost their troops — send them on long marches or join long-timer rallies so the troops are not sitting in the keep when an enemy rally lands. A zeroed keep (all troops killed) is devastating for morale and points. Ghosting prevents this.

Mid-event adjustments (Day 7 checkpoint)

By the midpoint of SvS (day 3-4 of the active event), you should have enough data to adjust strategy.

Questions to ask:

  • Are we ahead or behind on points? By how much?
  • Is our healing reserve on track to last the full 7 days?
  • Which point-earning activities are most efficient for our alliance?
  • Is the enemy server doing something unexpected?
  • Are our temples held or contested?

Common adjustments:

  • If ahead: maintain pace, protect the lead through defensive play, do not take unnecessary fights.
  • If behind: identify the highest-ROI point activities and focus there. Sometimes switching from rally-focused to temple-focused scoring can close a gap.
  • If healing is low: reduce combat frequency, focus on non-combat point activities.
  • If the enemy is pushing for a throne capture: coordinate server-wide defense immediately. Losing 50% of your score is catastrophic.

Endurance management

SvS runs for 7 days. Player fatigue is real and will cost you participation if you do not manage it.

Shift coverage:

  • Divide your alliance into timezone-based shifts. Each shift has a shift lead (R4 or trusted R3).
  • No single member should be expected to be active for more than 6-8 hours per day during SvS.
  • The R5 should be present for critical moments (throne attempts, hive defense) but can step back during stable periods.

Morale over 7 days:

  • Celebrate wins publicly and immediately. “Great rally, 3 kills” in Discord voice.
  • Do not dwell on losses. Brief analysis, then move forward.
  • Day 5 is usually the morale dip. Plan something engaging (a coordinated temple push, a targeted rally on a high-value enemy) to re-energize the alliance.
  • On the final day, acknowledge the effort regardless of outcome. “We showed up every day for a week. That is what defines this alliance.”

For the full picture of how SvS prep fits into your alliance leadership rhythm, see how to run an Evony alliance. Rally coordination specifics are covered in rally timing and coordination.