Skip to content

15 · Story Progression ​

Status: Recording Whiteout Survival's tutorial · Owner: TBD · Updated: 2026-09-30

Purpose ​

Record, chapter by chapter, the sequence Whiteout Survival uses to teach a new player — so Moksha's own onboarding can be designed against a known-good reference rather than from scratch.

Reference first, design later

Nothing here is Moksha's design yet. This page is a study of how Whiteout Survival teaches its systems and in what order. Moksha's own sequence gets written once the reference flow is fully recorded — Part 2 is reserved for it.

Sources are marked [src]. The chapter-by-chapter script in Part 1 is recorded from play, not from documentation, since the tutorial script does not exist in any text source.

Part 1 — Whiteout Survival's opening ​

The premise [src] ​

The world has ended. A catastrophic drop in global temperatures has plunged humanity into a perpetual glacial apocalypse.

The player is "the Chief", leading a small group of survivors to rebuild civilisation in a frozen wasteland. The core survival fantasy is explicit and physical: if the Furnace goes out, your people die; without warm shelter, they get sick. That is unusually strong framing for the genre — most 4X games open with abstract empire-building, this one opens with a threat you can feel.

The world has named factions — the Dawn Alliance and Phaethon — and recurring characters (Jessie the machinist, Molly, Bahiti) who appear as heroes.

The beat flow ​

#BeatPlayer actionSystem introducedGate
0Cold openWatchPremise: the world froze [src]—
1Light the FurnaceBuild / repair the FurnaceHeat, the survival threat, the HQ building [src]Start
2Take in survivorsBuild first ShelterPopulation as a resource [src]Furnace 1
3Cut woodBuild SawmillFirst production loop; build timers [src]Furnace 1–2
4Feed themBuild Cookhouse, then Hunter's HutFood economy; population upkeep [src]Furnace 2
5Dig deeperBuild Coal Mine, then Iron MineFour-resource economy complete [src]Furnace 3–4
6Tend the sickBuild ClinicPopulation health; a second failure stateFurnace 5
7RuleUnlock Chief's HouseEdicts — the first "I am in charge" beat [src]Furnace 6
8ArmUnlock Infantry Camp + BarricadeFirst troops, first defence [src]Furnace 7
9JoinUnlock Embassy, Arena, Infirmary, MonumentAlliance — the social hook [src]Furnace 8
10LearnUnlock Research Center, StorehouseLong-term investment [src]Furnace 9
11MarchUnlock Command CenterWorld map, rallies, real PvP [src]Furnace 10
12RecruitHero gacha opensCollection + monetisation [src]Chapter 3 — see note

The tutorial, chapter by chapter ​

Recorded from play. Each step is one guided action.

Chapter 1 ​

#Player actionWhat it teaches
1.1Gather wood by hand, then build the FurnaceResources exist; the Furnace is the heart of the settlement
1.2Build the Cookhouse, assign a villager to work in itFood, and that villagers are assigned to buildings
1.3Claim the task reward, then build the Sawmill and assign a villagerQuests are a resource source; production can be automated
1.4Build the Hunter's Hut, assign a villager, then upgrade itUpgrading, not just building
1.5Upgrade the Furnace to level 2The core building gates everything; the loop closes

Chapter 2 ​

#Player actionWhat it teaches
2.1Upgrade the Shelter; villagers arrive. Accept the refugees to gain workersWhere population comes from — housing capacity draws survivors
2.2Upgrade the Sawmill, then upgrade the FurnaceThe upgrade chain: feeder buildings first, then the gate
2.3Story beat: a snowstorm is coming → Chapter 3Raises a threat and hands off to the next chapter

Chapter 3 ​

#Player actionWhat it teaches
3.1Upgrade the Coal MineSecond-tier resource under pressure from the storm
3.2Upgrade the ShelterShelter as the answer to the threat
3.3Receive a hero; Exploration mode unlocks. Play exploration and collect its rewardsHeroes exist; a second resource faucet outside the city
3.4Fight until you lose. Hero recruitment opens to recruit more heroesPower is not automatic — and the fix is more heroes
3.57-day sign-in unlocks; claim the starter-pack reward to enhanceRetention and monetisation hooks, at the end of the chapter

Chapter 4 ​

Recorded at summary level only: Chapter 4 is entirely upgrading resource buildings and city buildings. No new system is introduced.

#Player actionWhat it teaches
4.xUpgrade resource production and city buildings throughoutConsolidation — no new mechanics

Individual steps not yet itemised.

Chapter 5 — complete ​

#Player actionWhat it teaches
5.1Upgrade the Furnace. The wait is long — the game teaches speed-upsTime is a currency, and it can be shortened
5.2Build the Iron Mine and upgrade it to level 5; more villagers can be assigned once it reaches level 5Building level raises worker capacity
5.3Build more Shelters and upgrade themHousing scales population; repeat a known loop
5.4Clear Exploration to stage 10; auto-skill unlocks at Explorer 6Exploration becomes semi-automatic

Chapters beyond 5 still to be recorded.

What the sequence is teaching ​

The order is doing deliberate work, and this is the part worth stealing:

  • Manual gathering before automation. 1.1 makes the player collect wood by hand before 1.3 hands them a building that does it forever. That contrast is what makes the Sawmill feel like a reward rather than a chore. Most games in this genre skip it and hand over production immediately.
  • One new verb per step. Build → assign → upgrade across 1.2–1.4. Nothing compound, nothing skipped. By 1.5 the player knows the entire city loop.
  • Chapter 2 answers the question Chapter 1 raises. Chapter 1 spends villagers without explaining where they come from; 2.1 supplies the answer. A small mystery, then its payoff.
  • Refugees are "accepted", not received. The phrasing implies the player could decline. Even if declining is never correct, being asked makes the player a ruler rather than a spreadsheet.
  • The storm arrives at the end of Chapter 2, not the start. Threat lands only after the player has a settlement worth losing — the same principle as putting the alliance at beat 9 rather than beat 1.
  • Chapter 3 turns the threat into mechanics. Coal then Shelter: fuel the fire, then shelter the people. The storm stops being narration and becomes something the player prepares for.
  • Survival first, empire later. Beats 1–6 are entirely about not dying. No combat, no PvP, no other players until the settlement is worth defending.
  • The alliance arrives at beat 9, not beat 1. Social hooks land after the player has something to protect. Earlier and they are noise.
  • PvP arrives at beat 11, last. By the time a player can be attacked they have ten beats of sunk investment.
  • Monetisation is gated behind completion, not offered on the first screen.
  • Chapter 3 ends by making the player feel weak, on purpose. Step 3.4 is a scripted loss — the player fights until they lose, and the game immediately offers hero recruitment as the answer. This is the single most commercially loaded beat in the whole sequence: it manufactures a need seconds before presenting the thing that satisfies it. It is also genuinely good teaching, in that a player who has only ever won learns nothing about why composition or power matter. Note both readings.
  • Exploration at 3.3 is a second faucet, and a different kind of play. Up to this point every resource came from buildings and quests. Exploration is the first content the player engages with outside the city loop, and it arrives right as the city loop starts to feel understood.
  • The monetisation ramp is 3.3 → 3.4 → 3.5. Receive a free hero, lose a fight, get offered more heroes, then get handed a 7-day sign-in and a starter pack. Free thing, felt need, the store, then a reason to come back tomorrow. That ordering is not accidental and it is the most transferable commercial lesson on this page.
  • Chapter 4 is a deliberate breather, and the rhythm matters more than its content. Chapter 3 ends in a burst — a hero, a new mode, a scripted loss, the store, a sign-in reward. Chapter 4 introduces nothing and simply has the player upgrade what they already own. That alternation — spike, then consolidate — is what stops onboarding feeling like a firehose, and it gives the systems from Chapter 3 time to settle before anything else is added. A tutorial that introduced something new in every chapter would teach less, not more.
  • Consolidation chapters are also where the economy is tuned. With no new mechanics competing for attention, Chapter 4 is where the player first feels build times and costs as the actual texture of the game. If the curve is wrong, this is the chapter where players quit — and it will look like boredom rather than difficulty.
  • 5.1 is the commercial hinge of the entire tutorial. The game deliberately gives the player an upgrade that takes too long, lets them feel the wait, and then teaches speed-ups as the answer. It is the same move as the scripted loss at 3.4 — manufacture the friction, then present the fix — but applied to time, which is the resource this genre actually sells. From this step onward every cost in the game is implicitly denominated in speed-ups whether the design intends it or not. If Moksha copies one beat knowingly, it should be this one, because copying it unknowingly is how a game ends up free-to-play by accident.
  • 5.2 reveals a rule the earlier chapters hid: building level raises worker capacity. Until now villagers were simply assigned. Here the Iron Mine at level 5 unlocks more assignment slots, which retroactively makes every earlier upgrade a labour decision too. Teaching a rule late, after the player has internalised the simple version, is efficient — but it only works if the UI makes the new capacity obvious at the moment it appears.
  • 5.4 converts Exploration from active to semi-automatic. The player clears ten stages by hand, then earns auto-skill. That ordering is the point: automation is a reward for competence, not a default. It also answers how the mode survives long-term — nobody hand-plays a hero battler for a year, so the game gives the grind away once it has been understood.
  • Each chapter has one idea. Ch.1 the production loop. Ch.2 population. Ch.3 the threat. That is a clean teaching structure and the most portable thing on this page.

Things to watch for while recording ​

Open observations to confirm on the next playthrough:

  1. Where does the first Shelter come from? 2.1 upgrades one and 1.2 assigns a villager, but no step builds housing. Likely the player starts with one — confirm.
  2. How many villagers does the player start with?
  3. Where is the Coal Mine built? 3.1 upgrades it; no recorded step builds it.
  4. Does the snowstorm do anything mechanically, or is it narration? This is the first point the game could hurt the player.
  5. Are failure states active during the tutorial — can villagers starve, can the Furnace go out?
  6. Where is the hard stop? Note the exact step where guided prompts end and the player is released.
  7. Chapter 4 in detail — which buildings, in what order, and how many steps. Worth itemising because it is the first chapter that is pure pacing, and the exact sequence is the clearest read on how the economy is tuned.
  8. Is Chapter 4 still guided, or has the game released the player by then and these are just quests?
  9. Where do the first speed-ups at 5.1 come from — granted, or already accumulated from quest rewards?
  10. What is "Explorer 6" — the Explorers' Cabin building level, or a player rank? The auto-skill gate depends on which.
  11. Does auto-skill fully automate Exploration, or only the skill casting?

Where the tutorial actually ends [src] ​

There are three different endings, and conflating them is the mistake:

  1. The guided hand ends early — the on-rails prompt sequence releases within the first session, once the basic build loop is understood.

  2. The tutorial gate ends when the gacha opens. Hero banners "unlock after you clear the initial tutorial" — the game withholds its primary monetisation until the player is invested. This is the meaningful boundary.

    Observation vs source

    Recorded play shows hero recruitment opening at step 3.4, inside Chapter 3. Either Chapter 3 is already past what the source calls "the initial tutorial", or the source is using the phrase loosely. Worth pinning down exactly — it decides where the real onboarding boundary sits.

  3. The beginner phase runs roughly 30 days, after which the player has an established city and army and moves into long-term strategy.

Part 2 — Moksha's story progression ​

Reserved — not written yet

Moksha's onboarding sequence will be designed once the Whiteout Survival flow above is fully recorded. Nothing is committed here on purpose: writing Moksha's chapters before the reference is understood would mean copying beats without knowing what they are for.

When it is written, the things to carry over are the structural lessons in What the sequence is teaching above — one verb per step, one idea per chapter, threat after investment — not the specific buildings.

Note also that Whiteout's premise does not transfer directly. Its opening threat is cold, which physically kills. Moksha's dynasties are tropical and monsoon-belt — Majapahit, Khmer, Srivijaya — so the equivalent pressure is flood, monsoon or drought, and the core building's stakes need their own justification. See Narrative & Tone.

Think about ​

Lessons to carry into Moksha's design later, not decisions about it now.

  • Do not move the alliance beat earlier. It is tempting — alliance membership is the strongest retention lever in the genre and the instinct is to get players into one fast. Whiteout puts it at beat 9 for a reason: a player with nothing to defend has no reason to value allies.
  • The first 60 seconds are the install decision, and they are mostly cinematic. Beats 0–1 are where players quit. That is the one place in a project of this kind where a pre-rendered sequence earns its cost.
  • The tutorial teaches beats 1–5 only. Everything after unlocks across days of play and is taught by quests and the alliance. Front-loading instruction is the most common onboarding failure in this genre.
  • The long story is a separate problem from onboarding. Whiteout sustains a multi-year narrative through faction conflict (Dawn Alliance vs Phaethon) delivered in events — none of which is in the tutorial. Worth recording separately once the opening is done.

Open questions ​

Questions about the reference, to answer by playing. Moksha design questions belong here only once Part 2 is being written.

#QuestionWhy it mattersOwner
1Where does the first Shelter come from?Ch.1 has no housing step
2How many villagers does the player start with?Ch.1 assigns before any exist
3Where is the Coal Mine built?3.1 upgrades one that no step builds
4Does the snowstorm do anything mechanically?Whether the threat is real or narration
5Are failure states active during the tutorial?Whether the game can hurt a new player
6At exactly which step do guided prompts stop?The real end of the tutorial
9Is the loss at 3.4 scripted and unavoidable, or can it be won?Whether the beat is teaching or manufacturing
10What does the free hero at 3.3 cost — is it a fixed character?Reference detail
11Does exploration stay relevant, or is it tutorial-only?Whether 3.3 introduces real content
7Is there a pre-rendered opening cinematic?Production reference
8How many chapters are there in total?Scope of the reference

Sources ​

Retrieved 2026-09-29:

Internal design document — work in progress.