Chapter 02 · ~30 min

Anatomy of a Mobile 4X

Every hit in this genre — from Empire: Four Kingdoms to Whiteout Survival — is the same machine wearing different skins. This chapter takes the machine apart, system by system, so you can reason about any 4X you're shown.

The three screens

A mobile 4X is really three interconnected games:

1. The city (base) — a builder game. Upgrade buildings, unlock systems, train troops, run research. This is where solo progression and most monetization live.
2. The world map — an MMO. A huge shared map (kingdom / state / world) dotted with resource tiles, monsters, event objectives, and thousands of other players' bases. This is where PvE farming and all PvP happen.
3. The alliance — a social layer with its own progression: alliance tech, territory, shops, gifts, chat. This is where retention lives.

Player attention flows in a loop: city produces power → power is exercised on the map → map conflict is organized by the alliance → alliance needs drive city priorities.

The timer economy

Everything in the city costs wall-clock time: construction, research, troop training, healing. Early timers are minutes; late-game timers are weeks per upgrade. Three design consequences:

• Session shape: the game trains you into many short check-ins — collect, re-queue, respond — plus longer scheduled sessions for wars and events.
• Speedups become the fungible currency of progress. Every timer can be finished with speedup items. Speedups arrive as event rewards, alliance gifts, and — at the margin — purchases. The entire economy can be denominated in "days of speedups".
• Queues are a monetization surface: a second builder, training queue slots, and queue-length increases are classic subscription and VIP perks.

Resources: produced, gathered, raided

Standard resource design has three faucets and one big distinction:

• Produced in-city (farms, sawmills, mines) — slow, safe-ish, idle.
• Gathered on the world map — park a march on a tile for hours; much higher yield, but exposed to attack (tile-hitting).
• Raided from other players — attacking a base loots its unprotected resources.

The big distinction: protected vs raidable. A warehouse/vault protects a baseline amount; resources above it are loot. Resource items from packs and events sit safely in inventory until opened — which is why serious players run "zero-resource" bases and open items only at the moment of spending. This tension (hoard safely vs grow fast) is deliberate: it makes raiding matter without letting raids destroy progression outright.

Troops, combat, and the hospital

• Tiers: troops come in tiers (T1…T10+), unlocked by base level and research. Higher tiers are disproportionately stronger — the race to the next tier (classically "T4") is a defining mid-game wall and spend trigger.
• The triangle: most games run rock-paper-scissors between three troop classes (e.g. infantry > cavalry > archers > infantry, wording varies). It creates scouting gameplay (see composition → counter it) without real-time skill demands.
• Combat resolution is asynchronous math in most of the genre: marches collide, a formula resolves stats/buffs/composition, and you read a battle report. Rise of Kingdoms' big innovation was making battles real-time on the map (troops visibly fight, you can micro and reinforce) — more on that in Chapter 4.
• The hospital is a retention valve: wounded troops go to a hospital to be healed (cheaper than retraining) instead of dying outright. Hospital capacity — and the rules for when troops die vs get wounded (PvE vs PvP, attack vs defense, war events) — is one of the genre's most important tuning dials, because mass troop death is the churn event. Healing costs also produce a huge post-war resource/speedup sink: wars literally generate demand.

Power: the universal metric

Every account has a visible power score — a weighted sum of buildings, research, troops, and heroes. It's the genre's level, gear score, and leaderboard in one. Two subtleties worth knowing:

• Power is partly vanity: troop power evaporates when armies die. A high-power account with dead troops is a "fat farm". Veterans read power composition, not the number.
• Power drives matchmaking and targeting — event brackets, war matchmaking, and who considers you prey. Some players deliberately keep power low ("power hiding") to punch up.

Heroes: the RPG layer

Most modern 4X games bolt a hero/commander system on top: collectible characters that lead marches, garrison the base, and buff the economy. Heroes carry the collection meta — rarities, levels, skills, gear, and (in most of the market) gacha acquisition with duplicate-based star-ups. This is the genre's second monetization pillar next to speedups, and its main long-term chase content. Rise of Kingdoms pairs commanders (primary + secondary skills interact); Whiteout Survival and Last War run hero squads with generational power creep. Notably, Goodgame's Empire predates this layer — its equipment/commander system is shallower and not gacha-driven, a real differentiator we'll dissect in Chapter 5.

Research and the tech wall

An academy runs research trees: economic (production, march capacity, gathering speed) and military (troop stats, tier unlocks). Research timers are the longest in the game — end-game techs run weeks — making research the deepest time-sink and a favorite target for speedup spending. The classic pacing pattern: each base-level band has a "wall" (a tier unlock or key tech) that converts progression pressure into either patience or payment.

The alliance: the actual retention engine

If you remember one system, remember this one. Alliances are where the genre's famous retention comes from:

• Help clicks: allies tap "help" on each other's timers, shaving minutes off. Trivial mechanic, brilliant design — it makes every timer a social touchpoint and gives lurkers a contribution verb.
• Rallies: group attacks on hard PvE targets and enemy players. The coordination (timing, troop types, who leads) is the genre's real gameplay skill.
• Alliance progression: tech trees fed by member donations, territory and banners claiming map area, alliance shops and daily gifts. When a whale buys a pack, the whole alliance often receives gift chests — whale spend literally showers loot on 99 other people, socially reinforcing spending.
• Obligation loops: scheduled wars, defense calls at 3am, Discord coordination. Guilt and loyalty toward specific humans is the churn barrier no feature can replicate.

Protection: shields, teleports, and the price of peace

• Newbie protection: fresh accounts can't be attacked for a few days — a grace period to reach an alliance's protective umbrella.
• Peace shields (bought or earned) make a base unattackable for 8h–3d. The genre's rule of thumb is "shield or die": any serious army sleeps shielded. Shields are effectively insurance monetization — recurring defensive spend that rises exactly when conflict (and fun) peaks.
• Teleports move your base: random (cheap escape), targeted (join the hive, or drop next to a victim). Map position is strategy; teleports monetize it.
• Anti-scout, fake reports, trap accounts: a whole counter-intelligence metagame exists; depth here is a hallmark of the older, hardcore titles.

The funnel: how a player's first month actually goes

1. Tutorial (minutes): forced build-and-fight sequence; modern titles front-load a casual minigame or narrative hook here (Chapter 4).
2. Protected growth (days): timers are short, dopamine is dense, the game feels like a cozy builder. Most D1–D7 retention is won or lost on this pacing.
3. First contact (week 1–2): protection ends. The player gets scouted, raided, or tile-hit. This is the churn cliff — and the moment the game funnels them toward joining an alliance ("get protected") and buying their first shield.
4. Integration (weeks 2–4): alliance events, first rally, first kill event, first war story. Players who reach a social role here retain for months or years; players who don't, leave. LiveOps' job is maximizing the share who make it.