Start with the current public-build boundary
The official itch.io page currently describes 24 levels, around 100 upgrades, and 16 unlockable units. That is the useful scope for a repeatable guide today. The same page notes that play can continue beyond the listed scope but may be unbalanced, so this article treats anything beyond the published 24-level count as an observation to verify rather than a promised campaign path.
Use a progression log, not a copied build order
When a run stalls, record the state that caused the stall. This makes a later replay comparable and helps separate a progression problem from a unit or economy problem.
| Moment | Write down | Why it matters |
|---|---|---|
| Before entering a new level | Factories, upgrade choices, and available units | Shows which tools were actually available when the level began. |
| When a wave breaks the line | Enemy pattern, frontline position, and the purchase made just before failure | Prevents a vague “late-game build” label from hiding the real decision. |
| After death or rollback | Returned level, retained resources, and lost factories | Lets you test the persistence rule and rebuild speed on the same version. |
What persists after death
The official description says that death returns the player to an earlier level. It also says upgrades and war points persist while factories are lost. The exact rollback formula is not documented in the source material reviewed here, so treat the returned level as a value to record in your own run rather than assuming a fixed number of levels.
- Spend a moment noting the upgrade tree state before restarting.
- Record war points separately from factory count; they do not follow the same rule in the official description.
- Rebuild a small baseline before judging whether the next attempt is faster.
Late-game and Level 30+ claims: how to read them
Players discuss Level 30+ progression, and an official screenshot shows a higher level, but the evidence does not establish a single optimal build beyond the current published scope. The latest devlog title previews subjects such as resource producers, new maps, and elite units; a title alone does not prove those features are in the current public build.
- Label a high-level tip with its build date and source.
- Separate a developer plan or preview from a feature you can load today.
- Retest unit, upgrade, and economy choices after any content update.
Browser save and play notes
The developer warns that saves do not work on Safari in the current web build. This guide has not verified a workaround, so use a supported browser or the official desktop demo when persistence matters. The homepage online-play section keeps the official launch link in one place.
Related decision guides
When a rollback removes your production base, use the factories, interest & purge guide to compare rebuild notes. For a unit choice that repeatedly fails a wave, use the unit overview while version-matched comparison evidence is collected.