⚔️ Evony Troop Layering Calculator

📖 Evony Troop Layering Guide

Evony Troop Layering Calculator: Build PvP Layers That Actually Survive

You've probably lost a march you thought was untouchable. One uniform block of your best tier, gone in a single report, while some player half your power walked away with a favorable trade. That's not bad luck. That's a layering problem, and it's exactly what an Evony troop layering calculator is built to fix.

What Troop Layering Actually Means in Evony

Layering is the practice of stacking small amounts of every troop tier and type into a single march instead of sending one giant block of your strongest troops. Instead of 2 million T13 archers and nothing else, a layered march might carry 1.8 million T13 archers as the core, then thinner bands of T12, T11, T10, all the way down, plus a mix of ground, mounted, and siege support.

Here's why that matters. Evony fights don't resolve instantly. Combat runs in rounds on a virtual battlefield where every unit starts 1,500 units apart and closes the distance based on speed. Mounted troops arrive first, ground troops follow, ranged units come next, and siege brings up the rear. Each layer in your march only engages one enemy layer per round, and the fight keeps going until every tier and type on both sides has taken its turn.

A single-tier march skips all of that nuance. It hits as one giant hit-or-miss block. A layered march, by contrast, spreads the fight across many separate tier-vs-tier engagements rather than one, which tends to protect your core troops from getting focused down in the opening rounds. This is the general logic most experienced players and community guides point to, rather than a mechanic you can verify down to the exact number, so treat it as the reasoning behind layering rather than a guaranteed formula.

Why an Evony Layer Calculator Beats Doing It by Hand

Manually splitting a march across 13 or 14 tiers, two or three troop types, and both attack and defense roles is the kind of math nobody wants to redo every time they train a new batch of troops. A troop layering calculator handles the split for you: you plug in your main troop type, your main tier, your troop count, and how thick you want each support layer, and it spits out a ready-made composition.

That matters even more as your server matures. Many players report that rally damage and defensive debuffs have climbed over time, and layer sizes that held up against a solo attack a year ago can start folding faster than expected. If your layers haven't been rebuilt since an earlier Keep level, it's worth revisiting the numbers rather than assuming, and battle reports are the real source of truth here, not any single guide. Run the numbers through our Evony Troop Layering Calculator before you commit resources, not after a battle report tells you it didn't work.

Attack Layers vs. Defense Layers

These two are not the same tool for the same job, and mixing them up wastes troops.

Attack (offensive) layers are built for speed and efficiency. Most of the march is your primary tier, with smaller support layers riding along underneath it. The goal is to get in, do damage, and get back out with minimal losses, so you're not padding the march with dead weight that just eats up your capacity.

Defense (trap) layers work the opposite way. There's no march cap holding you back inside your own city, so bigger is simply better here. A defensive setup should carry a real presence in every tier and type you have access to, because a well-layered attack can engage across multiple troop tiers and types, and you need something in every slot to trade with.

How Much Should Each Layer Actually Hold?

There's no single magic number, since layer size really depends on your Keep level, research, buffs, and how aggressive your server is. What follows are example defensive layer ranges that community guides commonly cite as a rough starting point, not a standard or "correct" size for each Keep:

Two players at the same Keep level can need very different layer sizes depending on research completion, general buffs, VIP level, and how aggressive their server's PvP scene is. Use these as a rough reference point, then build a layer set, take a few hits, read the battle reports, and adjust whichever layers folded fastest.

Siege March Layering for PvP

Siege units deserve their own paragraph because players consistently under-build them. Siege is generally regarded as having the longest range of any unit type in the game, which is why community guides treat it as engaging before your ground, mounted, or ranged troops close the distance. A siege layer that's too thin gets wiped before it contributes anything, and a march with zero siege support struggles to knock down walls or clear enemy siege of its own.

As a rough starting point rather than a fixed rule, many players keep siege somewhere around 10-20% of a PvP attack march's total composition, layered across their top 3-4 unlocked siege tiers instead of dumped entirely into the highest tier. The exact percentage that works best for you will depend on your research, generals, and what your alliance already brings to a fight, so treat this as a baseline to test and adjust. For a defensive keep, most players simply treat siege the same as every other type, meaning a real presence across every tier they have.

Evony Trap Layering: Winning the Loss Trade

Trap layering is really its own strategy, built around one idea: T1 troops are cheap to lose and expensive to kill in bulk. A T1 trap keep loads up on tier-one troops of a single dominant type, layered thin on top with a handful of higher tiers for research and general requirements. When an attacker's march crashes into that wall, they burn through expensive higher-tier units to clear cheap ones, and the power exchange favors you even if you technically "lose" the fight.

This only works for solo attacks and small hits, though. Reinforced rallies from a stacked alliance will walk through a pure T1 trap without much trouble, so if your server is rally-heavy, you need actual siege-based defense layers behind the trap, not just a thicker version of the same T1 wall.

How to Use the Calculator (Step by Step)

1. Choose the Main Troop Type. Decide what troop type you wish to use to form your march. Typical types include Ground, Mounted, Ranged, and Siege. This is the troop type that will form the bulk of your march.
2. Choose the Purpose. Decide what your purpose for creating this march is. Typical uses are PvP Attack, Defense, Boss Hunting, and Reinforcement. The calculator will build the layers accordingly, since a boss march and a rally defense march don't need the same shape.
3. Select the Main Tier. Select the highest tier of troops that will be your marching core, like T12. The calculator uses this tier as your main damage-dealing unit while generating the other layers around it.
4. Insert Number of Main Troops. Enter the number of troops from the selected tier that you want to use. For example: 1,567,900.
5. Choose a Layer Mode. Specify how thick you want the support layers to be. Common choices include Light (around 500 per layer, suitable for most PvP fights), Standard (a middle-ground option), and Heavy (bigger layers for more defensive or higher-stakes setups). Pick whichever matches your strategy.
6. Tap the Generate Layers Button. The calculator instantly builds out an optimized layer composition for you based on everything entered above.
7. Check Your Results and Copy Them. Your results show recommended troop counts for each tier and type. From here you can train these units directly, save the formation as a preset for future marches, or change the main troop count and regenerate the layers whenever your numbers change.

Hint: Keep your main troop count updated as you train more, and check in with your alliance or experienced players on layer mode conventions for your server. Even small support layers can make a real difference in how a fight plays out.

PvP Layering vs. PvE (Boss) Layering

It's tempting to build one layer set and reuse it everywhere, but PvP and PvE call for different logic.

For PvP, variety matters a lot. You want coverage across troop types so an opponent can't simply counter with the one type they specialize in. T1 layers can also be useful in some PvP setups because they may absorb losses before more valuable troops are affected, depending on the battle and your overall defense strategy.

For PvE (boss fights), your ideal composition shifts depending on the specific boss. Standard world bosses are commonly attacked with mounted troops by most players, but event bosses and special monsters often call for a different troop type or tier spread entirely, so it's worth checking guides or community notes for that specific boss before committing your best troops to the fight.

A Real Resource Cost Example

Once you've generated your layers, the next question is what they'll actually cost to train. That's where a troop cost calculator becomes useful alongside your layering plan.

Say your generated composition for a Keep 30 setup looks something like this:

Take each of those layer counts and run them through a troop cost calculator one tier at a time, then add up the results. That gives you your full Food, Wood, Ore, and Gold requirement across the whole composition before you train a single unit, so you can check you actually have the resources on hand rather than finding out halfway through a training queue.

Common Layering Mistakes

• Guessing layer sizes instead of calculating them. Random numbers leave you either too thin to absorb a hit or too thick to move efficiently.
• Setting your main troop percentage without a reason. That number should reflect your actual strategy, not whatever the default happened to be.
• Reusing an old max march size for a different march type. A gathering march and a Mixed PvP march don't share a cap. Rebuild it for the job at hand.
• Skipping siege entirely. Even a lean attack march needs some siege presence, and a defense keep without siege layers is giving up free range advantage.
• Copying someone else's layer setup wholesale. Their Keep level, research, and buffs aren't yours. Use their structure as a reference, then run your own numbers.

FAQ