7 Common Mistakes in Last War: Survival (and How to Avoid Them)

Every Last War: Survival player makes mistakes — the difference between good and great players is how quickly they learn. Here are the seven most common mistakes we see across thousands of server scans, and how to fix each one.

1. Gathering Without a Shield

Sending troops to gather resources without an active shield is the single biggest mistake. Your gathering army is completely undefended. Enemy scanners (including LW Spy) can detect your troops on resource tiles instantly. Always shield before sending troops out, or only gather during periods of known safety.

2. Rallying Shielded Targets

Nothing wastes more time than organizing a rally only to discover the target re-shielded while you were marching. Always verify shield status immediately before launching. Use LW Spy player search to confirm the target is still exposed seconds before committing your rally.

3. Ignoring Cross-Server Plunder

Many players only plunder on their home server, missing massive opportunities on neighboring servers. Cross-server plunder scanning reveals missions across multiple servers simultaneously. The best plunder targets are often on servers where no one is actively looking.

4. Poor Positioning During KvK

Bases clustered too tightly are vulnerable to area attacks. Bases too spread out cannot support each other. Use the Map Scanner to analyze your alliance positioning before KvK. Identify gaps in coverage and bases that are isolated from the main cluster.

5. Not Scanning Enemy Alliances Before War

Declaring war without intelligence is gambling. Always scan the enemy alliance first. Know their power distribution, shield habits, and base positions. Wars fought with intelligence are won before the first rally launches.

6. Plundering On a Hot Server Without Checking First

Cross-server plunder feels safe — your troops walk into another warzone, grab a Gold dispatch, and walk out. The mistake is treating every server the same. A server that is mid-KvK or mid-Desert Storm is full of active hunters scanning for inbound marches the moment they land. Before sending troops to a server you do not normally play, run a Cross-Server Plunder scan to see how many missions are even available; if the list is unusually short, it means locals are already farming hard, and your slow march will be noticed. The five-second check costs nothing and prevents losing a full march to a counter-rally on someone else's home turf.

7. Changing Heroes Without Telling Your Rally Leader

A rally is built around the hero composition members announced when they joined the queue. Swap your lead hero out 20 minutes before launch and the rally damage profile changes — sometimes catastrophically. Stun and slow heroes that the rally leader was counting on for crowd control suddenly are not there, and the rally fails against a target it should have crushed. Lock your rally lineup before any major event window and post a heads-up in the war channel if you have to change heroes mid-event. Newer alliances treat this as a personal preference; competitive alliances treat it as a coordination failure that costs the whole team.