Elphi'sAcademy
Battlefield Roles: More Than Rally Setter or Joiner
How to define useful battlefield jobs so every player knows what to do before the first building opens.
Learning Objectives
- Define roles by actions, not power.
- Match keep composition and march capability to jobs.
- Create backup responsibilities.
Why This Matters
A battlefield team loses time when every player waits for the same person to call every action. Roles turn a collection of strong keeps into a functioning unit.
Rally setter, battle tank, T1 trap, archer trap, ground trap, siege defense, ghost, and support joiner require different positioning, reinforcement, and risk decisions.
How Evony Actually Works
Roles should reflect what the keep can safely do: set rallies, join rallies, hold buildings, receive reinforcement, scout, ghost, clean buildings, or deny portals. Power alone does not define capability.
Step-by-Step Walkthrough
- Inventory each player’s march types, reinforcement capacity, keep defense, and availability.
- Assign a primary role and a backup role.
- Define where the player starts and what triggers movement.
- Assign communication channels and call terminology.
- Review after battle using reports and timing, not emotion.
Optimization by Spending Style
Free-to-Play
A reliable scout, joiner, cleaner, or portal player can create enormous value.
Low Coiner
Specialize in a role the account supports instead of imitating the largest keep.
Heavy Coiner
Build redundancy so the team does not collapse if one setter or tank is occupied.
Common Mistakes
- Assigning by power rank.
- Giving every player multiple conflicting jobs.
- No backup setter or caller.
- Changing roles mid-battle without communication.
Elphi's Recommendations
A role is a promise to perform specific actions.
Reliability beats theoretical power.
Quick Reference Checklist
- Capabilities inventoried
- Primary role assigned
- Backup role assigned
- Starting position defined
- Triggers defined
- Communication tested