Build a layered response
The official roster includes snipers, turrets, mortar squads and garrisons. Bombers and gatling gun helicopters provide air support. Safe zones and gates add civilian protection options.
How to compare units
Suggested approach: replay the same scenario and change one element at a time. Record the first breach, the number of civilians saved and when you needed air support. This is an editorial testing method, not a published tier list.
Mind the collateral damage
The developer warns that air strikes can kill civilians. Before calling one, inspect both the horde and the population around the target.
Damage, cost, range and upgrade comparisons are not yet verified for this guide.
A useful unit comparison needs a controlled scenario
A tier list needs evidence about cost, behavior, upgrades and outcomes. Until those values have been checked in the current build, use a comparison sheet instead of assigning letter grades.
| Record | Why it matters |
|---|---|
| Map and scenario | Establishes which attempt another player can reproduce |
| Unit and upgrade choices | Separates the unit from changes in its configuration |
| Position and opening plan | Shows the context of the deployment |
| First breach and final result | Captures both early behavior and the outcome |
Change a role before declaring a unit weak
When a deployment fails, describe the job you expected it to do and what actually happened. Then change one condition you can compare. This is an observation method, not a claim that every unit fits every role.
Keep emergency support in the same review
If you compare two opening layouts but use different support responses, the final result reflects both changes. Record interventions separately so you can revisit them. For score context, see civilian survival and scoring; for a repeatable run log, use the beginner guide.