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.
What connects depots, terrain and your advance?
The official descriptions say that capturing supply depots fuels your advance, cutting enemy supply lines can starve the enemy, and terrain dictates supply flow. Those mechanics connect three things you should inspect together: the force that needs supply, the depot or route supporting it, and the terrain between them.
A unit moving toward an objective is not evidence that its supply situation is healthy. Read its current in-game information, then inspect the operation behind that movement.
Before an advance: inspect the whole connection
- Start with the formation. Inspect the supply information the game currently provides for the units carrying out the operation. For a concrete starting point, the official Steam launch trailer shows a selected unit’s detail panel with a labelled Supplies row at 0:40. Inspect that row for an affected unit, then check other units involved instead of treating a troop total as a supply reading. Trailer evidence and version scope.
- Find the relevant depot and approach. Locate the supply feature you intend to rely on and inspect the ground between it and the formation.
- Read the terrain. The game models roads, towns, forests, swamps and elevation using geographic data. Consider them when choosing an approach; do not assume a straight line on the map describes its supply implications.
- Check the next stage, not just the current one. Ask whether another objective moves the formation beyond the support you have inspected or exposes a route behind it.
- Keep a fallback in the plan. Choose where you will reassess if supplies fall or the front changes, before fast-forwarding an extended movement.
For artillery support, the official description specifically recommends examining elevation maps and positioning artillery on high ground. That is a terrain consideration, not a guarantee that any hill solves a stalled attack.
When an attack stalls: use this diagnosis order
- First: is the formation carrying out the intended task?
- Inspect the units and the scope of the active plan. If the wrong force or area is involved, review command and orders before treating the problem as logistics.
- Then: are supplies running low?
- If yes, stop extending the offensive. Inspect the supporting depot, route and terrain, and consider pulling back as the official description advises. Do not assume a depot captured nearby instantly restores every unit.
- Next: what changed along the route or front?
- Compare the current situation with the approach you planned. A new objective, a changed front or an exposed route is a reason to pause and revise the next stage.
- If supply is not the visible problem: what else needs support?
- Inspect reconnaissance, artillery support, air operations and defensive conditions as relevant to the battle. Slitherine’s launch briefing describes these systems; a stalled attack alone does not prove which system caused it.
Start at the unit panel: read Supplies, check whether the issue affects one unit or several, then follow the depot/route/terrain checks above. The panel is an observation point, not proof of why the operation stalled. After changing the plan, observe the formation again before adding another commitment. This check keeps “attack harder” from becoming the default answer to every stalled operation.
Use enemy logistics as an objective
The official description explicitly supports starving the enemy by cutting supply lines. That gives an operation a different possible aim from a direct attack on every opposing unit.
As a planning exercise, identify the enemy supply connection you would like to disrupt, then inspect whether your own formation can reach and support that task. A diversion toward supply is still an operation with an approach, support and a fallback; it should not leave your force with the same problem you are trying to create for the enemy.
Use the scenario’s actual briefing to decide whether that task serves the required objective. A logistics opportunity does not override mission victory conditions.
What remains unknown?
The reviewed official pages do not publish supply consumption formulas, depot radii, resupply tick rates or a universal withdrawal threshold. Use the current game’s unit and supply information for those decisions. We also have no measured recovery timetable for wounded divisions.
For the broader learning loop, return to your first battle. Keep this guide focused on diagnosing the support for an operation rather than using it as an all-purpose mission walkthrough.
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.