Source-based planning guide, not a played mission walkthrough. Labelled UI examples come from the official Steam launch trailer, which mixes recorded builds; use your current tutorial if its interface differs. Planning decisions below are editorial applications of sourced mechanics.
Which level of command fits the task?
Slitherine’s launch briefing describes two levels of control: Zone Orders assign operational areas and objectives to whole formations, while individual-unit orders let you intervene directly. The product description says officers and companies carry out your high-level orders autonomously.
- “This formation should take responsibility for this area.”
- Use the formation-level planning approach. Make the objective and operational area clear, then observe how the formation carries it out.
- “This particular unit needs to do something different here.”
- Consider direct intervention. Recheck whether that local action still supports the formation’s wider task.
- “I cannot explain what the current plan is asking for.”
- Pause and inspect the force, area and stages involved before adding more orders. More input is not a substitute for a clear task.
The trailer’s Draw Order prompt at 0:40 gives a concrete drawing gesture: hold left-click for a line or enclosed area. It does not tell us how conflicting formation and direct orders are resolved. Check the recorded UI evidence. These are editorial choices about command scope, not a rule for how the game resolves conflicting orders. Use the released tutorials for exact selection and drawing controls.
Check the formation before issuing its plan
The published order of battle includes headquarters, regiments, battalions and companies. You can customize the chain of command and army composition, combine divisions into corps, and split units down to companies.
- Identify the formation you intend to task. Inspect its position in the current order of battle.
- Check the units attached to it. Match the operation to the infantry, tanks, engineers, anti-tank guns, artillery or scouts actually available.
- Assign supporting work deliberately. Decide whether the support belongs in the same operation or needs its own task.
- Inspect the result after unpausing. Confirm that the intended force and area are involved before extending the plan.
Make a multi-stage operation readable
Drawing directly on the map supports multi-step, multi-unit plans. The official description gives examples such as defence in depth, counterattacks, planned withdrawals and preparatory bombardments before a set-piece attack.
For a learning exercise, separate the operation into a first task, its support and the condition that prompts the next decision. For example: identify an approach, give support a purpose, and reassess after reaching the first objective. This illustrates how to reason about stages; it is not a verified opening for a named scenario.
Before adding a later stage, check supply and terrain. If an operation requires a withdrawal, include that possibility in the intent instead of assuming every stage must move forward.
When execution differs from your intent
- Wrong formation: inspect the current order of battle and which units the plan includes.
- Wrong operational area: review the formation-level task and the area assigned through the planning system.
- A local action needs attention: inspect that unit before choosing direct intervention; then recheck the wider plan.
- The operation cannot sustain another stage: pause, inspect supply and support, and reduce or revise the task.
Start by changing the part of the plan you can identify as wrong, then observe again. Exact order-priority rules, cancellation controls and command delays were not established by the official pages reviewed here.
Keep officers and campaign context in view
Officers can be hired, fired and promoted; keeping them alive allows them to gain veterancy and quirks. The persistent campaign also lets you requisition and upgrade units and rest wounded divisions. Inspect those consequences between battles before treating a formation as disposable.
A demo-era guide may describe a different command experience. The launch briefing lists Zone Orders, an expanded Army Constructor and improved AI and tactical systems among changes after Steam Next Fest. Check a tutorial’s version before following an exact input sequence.
The reviewed descriptions do not establish an optimal officer, unit ratio or hidden stat formula. For a complete first-session sequence, read plan, pause and review.
Sources checked October 13, 2026: Steam product description, Slitherine product description, and October 2 launch briefing. Scope: the October 2026 release; exact executable build not checked. Source and version notes.