Skip to main content
Main content
StrategyPublished 2026-03-265 min read

10 Alliance Leadership Tips for Last War: Survival

LW Spy · Independent fan website

Alliance leadership in Last War: Survival requires a combination of strategic thinking, communication skills, and information management. The best leaders are not always the highest power — they are the ones who make the best decisions with the information available. Here are 10 tips that will make you a more effective R4 or R5.

1. Share Intelligence, Not Just Orders

Instead of just telling members who to attack, share why. Show them the scan results — the exposed targets list, the shield timers, the alliance map. When members understand the reasoning, they execute better and make smarter independent decisions when leadership is offline.

2. Scan Before Every Major Decision

Before declaring war, before rallying, before migrating — scan first. Use the Alliance Scanner to map the enemy before engaging. Use the Shield Tracker before sending rallies. Intelligence eliminates guesswork and prevents costly mistakes.

3. Use Discord for Coordination

In-game chat is limited. Set up a Discord server with the LW Spy bot. Create channels for war coordination, intelligence sharing, and general discussion. The Discord bot lets any officer run scans and share results instantly with the whole team.

4. Enforce Shield Discipline

The number one cause of alliance losses is members getting attacked while unshielded. Run regular Exposed Target scans on your own alliance. Name and shame members who are consistently exposed. Make shield discipline a requirement, not a suggestion.

5. Rotate Rally Leaders

Do not burn out your top players by making them lead every rally. Train multiple rally leaders and rotate them. Use LW Spy to identify targets and assign them to different leaders based on availability and troop composition.

6. Triage Your Tools: Discord Bot vs Web Dashboard

The Discord bot is for in-the-moment war-room calls — instant, visible to every officer at once, perfect for "is target X still exposed right now." The web dashboard is for the deeper work: building a daily archive of enemy positions, comparing how a rival alliance shifted across the week, looking at the same scan with five filters until you find the gap. Train your officers to use the bot for live coordination and the dashboard for planning. Alliances that try to do everything in Discord chat lose the historical context that wins long campaigns; alliances that try to do everything in the dashboard react too slowly during live wars.

7. Respect Pacts and Know Your Server's Scanning Etiquette

Different servers have different unwritten rules about who is fair game to scan. Some servers consider any alliance scan an act of aggression; others treat scans as routine. Learn your server's convention before scanning a marginal alliance — a single ill-timed Alliance scan on a large neutral can flip them into an enemy that ruins your next event. Faction Pacts (the same-faction non-aggression mechanic introduced in Season 6) make this even more important: scanning inside your own faction can break the pact in a way that costs the entire alliance access to faction-tech donations. When in doubt, ask the target alliance's R5 first and treat the scan as a diplomatic act, not just a tool action.

8. Run a Weekly Internal Scan on Your Own Alliance

Most R5s scan enemies daily and never scan their own alliance. Once a week, run an Alliance scan on your own tag and read it like an outsider would. Which of your members would an enemy raider target first? Who is sitting unshielded for hours at a time? Whose power has stagnated for two weeks (a sign of disengagement before they quit)? This audit catches the issues that destroy alliances quietly — drift, neglect, and members who have effectively left without saying so. Pair it with an Exposed Targets scan filtered to your alliance tag if your subscription supports it; what you see is exactly what your enemies see.

Scan your server with LW Spy

Explore supported scans, current plans and data limitations.