1. Give the Army a Purpose
Write one outcome before moving: defend a route, pressure a rival, protect a lordship, or gain a better position. A purpose makes it easier to decide what not to chase and prevents a tactical victory from becoming a strategic loss.
- State the objective in one sentence.
- Choose the terrain that supports it.
- Know what result is “good enough.”
2. Build a Readiness Check
Before a battle, check formation jobs, reserve position, commander exposure, and retreat options. This page does not assume hidden economy or unit rules; it focuses on decisions visible in public battle coverage.
- Who holds, who flanks, and who remains in reserve?
- Where can damaged troops withdraw?
- What terrain changes the first order?
3. Use a Retreat Threshold
A retreat is not automatically a failure. Define the moment when preserving trained troops and commanders is worth more than contesting the current field. That threshold creates clearer morale and command decisions during a messy fight.
- Watch for a spreading morale break.
- Do not expose the commander to repair every problem.
- Protect the campaign’s next decision.
4. Turn Fights Into Notes
After every engagement, record terrain, first order, morale change, retreat timing, and campaign consequence. These notes create a useful guide archive when official systems become more detailed.
Battle guide · World and route notes · Release status
Update boundary: use the
official Steam page and official developer updates before adding named units, platforms, multiplayer, or progression systems. This guide deliberately avoids presenting unconfirmed mechanics as fact.