Skip to content

08 · Progression & Ages ​

Status: Draft — ages mapped to Palace levels · Owner: TBD · Updated: 2026-09-29

Purpose ​

Define long-term advancement: the age system borrowed from Age of Empires, the tech tree, and what a player is working toward at every stage.

To define ​

Ages ​

Ages are bands of Palace level, not a separate track. See City & Buildings for the full 30-level unlock table.

AgePalaceThemeKey unlocks
I — Founding1–9Ruins, survival, first wallsFour resources, Court, Infantry / Marksman / Lancer Camps, Walls, Embassy, Library. Counter triangle completes at Palace 9
II — Rise10–17Armies, alliance, territoryWar Room, Muster Office, Drill Yard, Market, Armoury, Dynasty Unique building (16)
III — Zenith18–25Monuments, the golden ageWar beasts, Mastery Forging, Regalia, wall tier 2, advanced edicts
IV — Twilight26–30Peak power, the fall approachingElite troop tiers, alliance wonder, final research
AscensionA1–A10The cycle begins againPrestige tiers past the cap

Ascension ​

Whiteout Survival continues past its level cap with Fire Crystal tiers — a straightforward power extension. Moksha's version, Ascension, should do more than extend numbers: it is where the title cashes out. The dynasty reaches its peak, falls, and begins again carrying something forward.

Three shapes, weakest to strongest:

  1. Pure extension — A1–A10 are simply more levels. Safe, boring, exactly what the competition does.
  2. Soft rebirth — the city keeps its buildings but converts accumulated progress into permanent dynasty traits. Some loss, large permanent gain.
  3. True rebirth — the city resets to Age I with permanent bonuses and a visibly changed dynasty. Thematically perfect, mechanically the riskiest thing in the document, and the only version that would make Moksha structurally different from its competitors.

Option 2 is the defensible middle. Option 3 is the one worth prototyping if the team has appetite, because it also solves server calcification (see Seasons).

Think about ​

  • Age advancement is the best pacing tool you have. It is a rare, loud, celebratory beat in a genre made of small increments. Make each one a genuine event: the city visibly transforms, new units unlock, there is a cutscene or ceremony. Do not let it become "core building hit level 10".
  • Dynasty-specific age names are cheap identity. Majapahit's ages should not be called the same thing as Aksum's. Almost free, and it deepens the fantasy.
  • The "decline" question is the game's most interesting design fork. Every dynasty here actually fell. Do you model that? A late-age decline phase — or a Moksha rebirth that resets the city for permanent bonuses — would be thematically perfect and mechanically distinctive. It is also risky: players hate losing progress, and prestige systems need very careful tuning. Explore it properly before dismissing it; it may be the game's signature system.
  • Too many parallel tracks is the genre's UX disease. City level, account level, age, hero levels, tech tiers, VIP, alliance rank, season pass. Each feels additive; together they are unreadable. Cap the number of tracks a player must think about at once.
  • Power score is a social object, not a stat. It is what players compare, brag about and use to pick targets. Whatever you put in it becomes what players optimise — so if you want composition to matter, do not let raw troop count dominate the number.
  • Design the endgame before launch, not after. Maxed players who run out of progression either quit or become your most disruptive community members. Give them a job: alliance leadership, seasonal competition, prestige.

Open questions ​

#QuestionBlocksOwner
1How many ages at launch?Art, scope, economy
2Is there a decline/rebirth mechanic?Identity, economy, retention
3Shared ages or per-dynasty?Art budget, balance

Internal design document — work in progress.