Appearance
06 · Units & Battle
Status: Draft — Whiteout Survival troop model adopted as baseline · Owner: TBD · Updated: 2026-09-29
Purpose
Define armies and combat. The roster and stats below are taken from Whiteout Survival as a starting baseline, to be tuned and diverged from before ship.
To define
Two combat modes
Moksha has two separate combat systems. They share nothing but the fiction.
| Mode | Decided by | Content |
|---|---|---|
| 6.1 Exploration | Hero stats and level | Solo PvE, outside the city |
| 6.2 Expedition | Trained troops; unit choice driven by the battle | World map, sieges, rallies, PvP |
Everything on this page — the roster, base stats, counter triangle and damage model — applies to Expedition. Exploration is resolved entirely by heroes and ignores trained troops.
Unit roster
Three classes. No siege class — walls are attacked by ordinary troops.
| Class | Role | Trained at | Palace |
|---|---|---|---|
| Infantry | Tank. High defence and health, low damage | Infantry Camp | 7 |
| Marksman | Damage dealer. High attack and lethality, very fragile | Marksman Camp | 8 |
| Lancer | Balanced. Middling everything, highest lethality | Lancer Camp | 9 |
The counter triangle
Infantry beats Lancer · Lancer beats Marksman · Marksman beats Infantry. The counter bonus is +10% attack — notably small. See Think about.
Base stats
Per-troop base values, before research, hero, gear and buff modifiers. Load is resource-carrying capacity for gathering, not a combat stat.
Infantry
| Tier | Attack | Defense | Lethality | Health | Load |
|---|---|---|---|---|---|
| T1 | 1 | 4 | 1 | 6 | 108 |
| T2 | 2 | 5 | 2 | 7 | 124 |
| T3 | 3 | 6 | 3 | 8 | 142 |
| T4 | 4 | 7 | 4 | 9 | 164 |
| T5 | 5 | 8 | 5 | 10 | 188 |
| T6 | 6 | 9 | 6 | 11 | 217 |
| T7 | 8 | 11 | 7 | 12 | 249 |
| T8 | 9 | 13 | 8 | 13 | 287 |
| T9 | 10 | 14 | 9 | 14 | 330 |
| T10 | 13 | 15 | 10 | 15 | 379 |
| T11 | 15 | 17 | 12 | 17 | 400 |
Lancer
| Tier | Attack | Defense | Lethality | Health | Load |
|---|---|---|---|---|---|
| T1 | 4 | 2 | 5 | 2 | 108 |
| T2 | 5 | 3 | 6 | 3 | 124 |
| T3 | 6 | 4 | 7 | 4 | 142 |
| T4 | 7 | 5 | 8 | 5 | 164 |
| T5 | 8 | 6 | 9 | 6 | 188 |
| T6 | 9 | 7 | 10 | 7 | 217 |
| T7 | 10 | 8 | 11 | 8 | 249 |
| T8 | 11 | 9 | 12 | 9 | 287 |
| T9 | 12 | 10 | 13 | 10 | 330 |
| T10 | 13 | 11 | 14 | 11 | 379 |
| T11 | 15 | 13 | 16 | 13 | 400 |
Marksman
| Tier | Attack | Defense | Lethality | Health | Load |
|---|---|---|---|---|---|
| T1 | 5 | 1 | 5 | 1 | 108 |
| T2 | 6 | 2 | 7 | 2 | 124 |
| T3 | 7 | 3 | 8 | 3 | 142 |
| T4 | 8 | 4 | 9 | 4 | 164 |
| T5 | 9 | 5 | 10 | 5 | 188 |
| T6 | 10 | 6 | 11 | 6 | 217 |
| T7 | 11 | 7 | 12 | 7 | 249 |
| T8 | 12 | 8 | 13 | 8 | 287 |
| T9 | 13 | 9 | 14 | 9 | 330 |
| T10 | 14 | 10 | 15 | 10 | 379 |
| T11 | 16 | 12 | 17 | 12 | 400 |
Reading the table
Note the shape rather than the numbers. Infantry inverts the others — defence and health above attack and lethality. Marksman is the mirror image: T1 Marksman has 5 attack and 1 health; T1 Infantry has 1 attack and 6 health. Lancer sits between them but carries the highest lethality at most tiers, which matters because lethality bypasses defence entirely.
Load is identical across all three classes at every tier — gathering speed does not depend on troop type.
Damage model
The four stats
| Stat | What it does |
|---|---|
| Attack | Damage that must chew through the enemy's Defense before reaching Health |
| Defense | Absorbs incoming Attack. While it holds, Health is untouched by ordinary attacks |
| Lethality | Bypasses Defense entirely and strikes Health directly |
| Health | The pool that must be emptied to kill the troop |
The pairings are Attack ↔ Defense and Lethality ↔ Health. This is the central mechanic and the reason the roster is not simply "big number wins": a stack of high-defence Infantry is nearly immune to Attack but still bleeds to Lethality, so composition and stat focus both matter.
Confirmed battle behaviour
- Turn-based resolution. Both sides pick targets and attack simultaneously each turn.
- Front-row targeting. Troops attack the enemy front row first; when it is eliminated they move to the next row.
- Counter bonus is +10% attack against the class you counter.
- Casualty split varies by battle type. In player-city battles, 35% of the attacker's casualties die; the rest are wounded. Other battle types send casualties to the Infirmary with overflow dying.
The formula is not public
Century Games has never published the damage equation
Community wikis, calculators and guides describe what the stats do but none states the actual equation. The community works empirically from testing. Anything presented online as "the Whiteout Survival damage formula" is reverse-engineered approximation, not documented fact — treat it as such.
This means Moksha cannot copy the formula. It has to define its own that reproduces the observed behaviour.
Proposed formula for Moksha
This is Moksha's own design, not Whiteout Survival's. It reproduces the observed behaviour — two damage channels, defence as a shield against one of them only — in a form that is cheap to compute server-side and explicable to a player.
Per attacking troop, per turn, against one defending troop:
effective_attack = Attack x (1 + counter_bonus) x (1 + attack_buffs)
effective_lethality = Lethality x (1 + counter_bonus) x (1 + lethality_buffs)
counter_bonus = 0.10 if attacker counters defender, else 0
# Channel 1 — blocked by Defense
defense_pool = Defense x (1 + defense_buffs)
if defense_pool > 0:
absorbed = min(effective_attack, defense_pool)
defense_pool = defense_pool - absorbed
health_dmg_1 = effective_attack - absorbed # overflow leaks through
else:
health_dmg_1 = effective_attack
# Channel 2 — ignores Defense entirely
health_dmg_2 = effective_lethality
total_health_damage = health_dmg_1 + health_dmg_2Open decisions this formula leaves:
- Does Defense regenerate between turns, or is it a depleting pool for the whole battle? A per-turn reset makes Infantry far stronger and makes Lethality the only reliable way to kill them. A depleting pool makes long battles swing.
- Is Defense per-troop or per-stack? Per-stack is far cheaper to compute at the scale of a rally with hundreds of thousands of troops.
- Does Attack overflow leak to Health, as written above, or is it fully absorbed? Full absorption makes Lethality mandatory.
Answer these three and the combat model is closed.
Think about
- The +10% counter bonus is small, and that is a deliberate choice worth understanding before adopting it. A 10% attack edge does not let a countering army beat a significantly larger one. It nudges composition without letting skill overcome investment — which protects spending. A bonus in the 1.5x–2.0x range would instead make composition decisive and let a smaller, smarter army win. If Moksha keeps the "thinking beats spending" pillar from Overview, 10% is too low and the pillar is dead on arrival. This is the single most important number on this page.
- No siege class means walls are just a health pool. Any troop can attack them at full rate. That is simpler to build and to explain, but it removes a strategic layer: there is no escort decision, and no unit whose whole job is breaking a city open. Worth revisiting if sieges feel flat in playtest.
- Lethality is the interesting stat and the one to build Moksha's identity on. Attack-vs-Defense is a standard shield mechanic. Lethality-bypasses- Defense creates a genuine composition puzzle: stacking pure Infantry is punished by Lethality, stacking pure Marksman dies to anything that closes. If you want a deeper combat layer than the competition, extend this rather than adding classes.
- Stat values scale gently and that matters. T1 to T11 Infantry attack goes 1 to 15 — roughly 15x across the entire game. Power growth therefore comes overwhelmingly from research, gear, heroes and troop count, not tier. Tier unlocks are pacing gates, not power spikes. Budget your progression accordingly.
- The 35% death rate is a retention dial. Two thirds of casualties coming back wounded is generous — it keeps losers in the game and keeps the map active. Healing them is the resource sink (see Economy). Raising that 35% makes war more costly and the server quieter.
- Copying stats is fine; shipping them is not. Base stats are functional game data, not protectable expression, and using them as a tuning baseline is ordinary practice. But shipping a game whose troop table matches a competitor's exactly invites the obvious comparison, and these numbers are tuned for their economy, event calendar and progression curve — not yours. Treat this table as the starting point for your own spreadsheet.
- This is still an auto-resolve model. Nothing above requires player input during battle. If Moksha wants to deliver the Age of Empires half of its pitch, that has to come from somewhere else — pre-battle composition depth, formations, or a tactical layer. Unresolved, and still the biggest question in the document.
Open questions
| # | Question | Blocks | Owner |
|---|---|---|---|
| 1 | Auto-resolve, tactical, or real-time? | Everything | |
| 2 | Is the counter bonus 10%, or higher to support the strategy pillar? | Whether composition matters | |
| 3 | Does Defense regenerate per turn or deplete across the battle? | Combat maths | |
| 4 | Is Defense per-troop or per-stack? | Server cost at rally scale | |
| 5 | Does Attack overflow leak to Health? | Whether Lethality is mandatory | |
| 6 | Walls: health, gates, garrison strength? | Siege viability, server temperature | |
| 7 | Casualty split — keep 35% death in city battles? | War pacing, retention | |
| 8 | Launch with all 11 tiers, or fewer? | Scope, balance |
Sources
Retrieved 2026-09-29:
- One Chilled Gamer — Troop Guide — base stat tables T1–T11
- BlueStacks — Troops Guide — counter triangle
- Endless Winter Fans — Troop Guide — Attack/Defense and Lethality/Health mechanics
- Century Games Help Centre — Combat FAQ — turn-based resolution, targeting, 35% casualty death rate
- Whiteout Survival Wiki — Combat Stats & Special Bonuses — buff stacking