Appearance
6.1 · Exploration Combat
Status: Draft — mode defined, mechanics open · Owner: TBD · Updated: 2026-09-30
Purpose
Define the hero-driven combat mode. Exploration is the solo, PvE, hero-led half of the combat design — trained troops play no part in it.
The rule
Exploration outcomes are decided by heroes: their stats and their level.
Nothing the player does in the barracks affects an Exploration fight. A player with a maxed army and weak heroes loses; a player with strong heroes and no army wins. The two combat systems are deliberately separate — see 6.2 Expedition.
| Exploration | Expedition | |
|---|---|---|
| Decided by | Hero stats and level | Trained troops |
| Troops involved | No | Yes |
| Heroes involved | Yes — entirely | To be defined |
| Opponent | PvE | PvE and PvP |
| Introduced | Chapter 3 of onboarding (Story Progression) | After the world map opens |
To define
Think about
This is the mode that justifies heroes existing. If heroes also dominated Expedition, the army would be decoration. Confining hero power to Exploration gives the collection system its own arena and keeps troop training meaningful. That is a cleaner answer to "how much of total power sits in heroes?" than most games in this genre manage — see Heroes.
Exploration is a resource faucet, and that makes it an economy problem, not just a combat one. It is introduced in onboarding as a second source of income outside the city. Decide early what share of a player's daily resources it should provide — too generous and the city loop stops mattering, too stingy and players stop playing it after the tutorial.
Solo PvE content is where a hero roster gets shown off. It is the only place a player sees their heroes act, since Expedition is about troop counts. Skill animations, banter, boss fights — this is where the collection becomes emotionally worth having. Budget accordingly.
Decide whether this is active or idle. Idle Exploration (set a team, collect later) fits the genre's check-in rhythm and costs little to build. Active Exploration (stage-by-stage, player choices) is real content and a genuine differentiator, but it is a second game to balance and animate.
Worth noting how the reference handles it: Whiteout Survival makes the player clear ten stages by hand, then grants auto-play as a reward (see Story Progression, step 5.4). Automation is earned, not default — the player learns the mode before being allowed to skip it. That is probably the right answer for Moksha too: it gets the teaching value of active play without expecting anyone to hand-play a hero battler for a year.
Level is doing a lot of work in "stats and level". If level alone decides outcomes, Exploration becomes a pure power check and the roster stops mattering — any hero at level 50 beats any hero at level 40. If stats and composition matter, the collection has depth. This is the same tension as the counter bonus in Units & Battle, and it wants the same answer.
A hero-only mode is the natural home for a difficulty curve. Troop-based combat scales by numbers, which is blunt. Hero combat can scale by demanding better teams, which teaches. If Moksha wants anywhere that rewards thinking over spending, this is the most achievable place to put it.
Open questions
| # | Question | Blocks | Owner |
|---|---|---|---|
| 1 | Active first, then earned auto-play — or idle from the start? | Scope, tech, content budget | |
| 2 | Team size and is there a formation? | Hero design, UI | |
| 3 | What share of daily resources should Exploration provide? | Economy balance | |
| 4 | Do hero skills fire automatically? | Whether the player makes decisions | |
| 5 | Is there an attempt/stamina limit? | Session length, monetisation |