WarCollege
Reading Scouts and Battle Reports - Battlefield Intelligence
Strong PvP players do not attack randomly. They read scouts, recognize keep types, estimate rally requirements, choose the correct counter, and use every battle report to decide what happens next.
Mission Objectives
- Read a scout report in under thirty seconds.
- Identify troop composition, trap signals, buff profiles, and siege danger.
- Use the first report to select the next rally instead of repeating blindly.
Why This Matters
A scout shows the current condition of the target before combat. A battle report shows what actually happened after combat. One answers whether to attack; the other answers how to improve the next attack.
The first five scout checks are total troop count, dominant troop type, T1 walls, buff strength, and siege numbers.
How Battlefield Actually Works
Scout reports reveal troop numbers, tiers, buffs, generals, equipment, and visible defensive structure. Large T1 mounted counts usually indicate a trap keep. Heavy high-tier ranged layers often indicate ranged defense. Large siege concentrations may require siege clearing before other rallies can work.
Very high attack buffs reveal the troop type the defender is built to use, but HP, defense, reinforcements, wall generals, sub-city debuffs, and troop composition determine how difficult the keep actually is.
Battle reports reveal kills, wounds, layer performance, surviving troop types, power exchange, and the defensive component costing the most points.
A field estimate for a target with roughly 10M defending troops is that each additional 1000% buff advantage may require roughly 10M to 15M more rally troops. This is a planning estimate, not a guarantee; composition, debuffs, gear, range, reinforcements, dragons, and report sequence can change the result.
Typical rough estimates: 1500% may require one 20M-25M rally; 2500% may require siege then ranged totaling 30M-40M; 3500% may require 40M-55M; 4500% may require 55M-75M; 5500% may require 70M-100M; 6500%+ often requires 100M+ across multiple coordinated rallies.
Battle Plan: Step by Step
- Read total troop count and determine whether the target can be removed in one rally or needs a sequence.
- Identify the dominant troop type and expected counter.
- Check for T1 walls, high-tier defensive layers, and reinforcement signs.
- Compare the highest attack, defense, and HP buffs, then identify what the keep is designed to do.
- Check siege numbers and decide whether siege clearing is required.
- After the first rally, inspect killed and wounded troops, survivors, damage by troop type, and power exchange.
- Choose the next action: another siege rally, ranged, ground, mounted, reinforcement stripping, a different setter, or disengagement.
Optimization by Account Style
Free to Play
Become fast and accurate at scouting. Good intelligence lets smaller players create enormous value without risking a march.
Low Coiner
Use field estimates to avoid targets that require more volume than the alliance can fill.
Heavy Coiner
Do not let high buffs replace analysis. The wrong rally into the wrong defense is still an expensive donation.
Common Battlefield Mistakes
- Choosing a march simply because it is your strongest.
- Looking only at attack buffs and ignoring HP, defense, troops, and reinforcements.
- Sending the same rally again without reading the first report.
- Treating the rally estimates as exact mathematics.
- Ignoring siege and T1 trap signals.
Evony Logic & Philosophy - The ELPhi System
Battlefield intelligence is not about finding someone you can attack. It is about finding someone you should attack.
Every scout can prevent a bad report. Every report should produce a decision.
Scout. Counter. Rally. Read. Adapt.