Skip to content

6.2 · Expedition Combat ​

Status: Draft — mode defined, mechanics open · Owner: TBD · Updated: 2026-09-30

Purpose ​

Define the troop-driven combat mode. Expedition is where the army the player trains actually fights — the world map, sieges, rallies and PvP.

The rule ​

Expedition outcomes are decided by the troops the player trains. Which unit class to send is decided by the battle at hand — the scenario determines what is effective, so composition is a per-battle decision rather than a single optimal army.

That second rule is what makes the counter triangle matter. If one army composition won everywhere, Infantry / Lancer / Marksman would be a stat choice rather than a tactical one. Tying effectiveness to the specific engagement is what forces the player to keep all three trained and to scout before committing.

The unit classes, base stats, counter triangle and damage model all live in Units & Battle and apply here, not to 6.1 Exploration.

Confirmed reference behaviour [src] ​

From Whiteout Survival, whose Expedition model this follows:

  • Turn-based. Each turn, both sides select targets and attack simultaneously.
  • Front-row targeting. Troops attack the enemy front row first; when it is eliminated they move to the next row.
  • Casualty rates vary by battle type. In player-city battles, 35% of the attacker's casualties die; the rest are wounded and recoverable.

To define ​

What drives unit choice ​

"The event of the battle" needs pinning down, because there are three quite different readings and they produce three different games:

ReadingHow it worksConsequence
Enemy compositionThe defender's troop mix determines what counters itClassic. Rewards scouting. The most conventional choice
Scenario typeThe battle kind dictates the effective class — sieges favour one, open field another, ambushes a thirdRewards keeping a broad army. More authored, more teachable
Scripted eventEach battle explicitly states which class it calls forClearest to a new player, but removes the deduction

Recommendation: scenario type, with enemy composition layered on top. The scenario tells the player roughly what to bring, and reading the defender's actual mix is the finer-grained skill. That gives a beginner a rule to follow and an expert something to master, which is the usual shape of a good system.

Think about ​

  • Two combat systems is two balance problems and roughly double the combat tech. That is the real cost of splitting Exploration and Expedition, and it should be acknowledged in Scope. The payoff is worth it — heroes and troops each get an arena where they matter — but it is not free, and a prototype should probably build one properly before starting the other.
  • This mode has to carry the Age of Empires half of the pitch on its own. Exploration is hero-driven and mostly automatic; if Expedition is also fully auto-resolved, no part of Moksha delivers strategy the player executes. Making unit choice scenario-dependent is a genuine step toward that, because it is a real decision made before the fight. Whether there is also a decision during the fight is still the biggest open question in the document.
  • Scouting becomes load-bearing. If the battle determines the right unit, the player must be able to find out what they are walking into. Without scouting, "bring the right class" is guesswork, and guessing that costs an army is how players quit. The Watchtower in City & Buildings is where this lives.
  • The battle report is the teaching surface for the whole system. A player who brought the wrong class needs to see that on one screen, not infer it. If the report only shows casualties and a win/loss, the counter system is invisible and players conclude they lost because they did not spend.
  • Decide whether heroes touch Expedition at all. A clean split — heroes for Exploration, troops for Expedition — is easy to explain and protects troop training from being made pointless. But heroes leading marches is the genre norm and a strong monetisation lever. If they do contribute, cap it, and write the cap down in Heroes.
  • Wounded-versus-dead is the war economy. The 35% reference figure keeps two thirds of losses recoverable, which keeps beaten players in the game and the map active. Healing them is the resource sink. Raise that number and the server gets quieter; lower it and war costs nothing.

Open questions ​

#QuestionBlocksOwner
1Which reading of "the event of the battle"?Whether composition is deduced or told
2Do heroes contribute to Expedition, and how much?Hero value, troop relevance
3Is there any player decision during a battle?The strategy pitch
4Can the player scout before attacking?Whether unit choice is skill or guesswork
5Casualty split per battle type?War pacing, retention
6Stack size and classes per march?Server cost, tactical depth

Sources ​

Internal design document — work in progress.