The most important expedition skill in Pax Autocratica is not aim. It is knowing how much risk the current run can still support.
Staying out gives you more encounters, resources, prisoners and opportunities to strengthen the run with Core Fragments. Returning protects extracted value and gives the colony a chance to recover, but community-observed interface warnings state that returning also resets expedition progress and the Core Fragments collected during that expedition.
The correct decision changes every run.
Start with an objective
Before choosing soldiers, decide what the expedition is for:
- gather a specific resource;
- increase sector progress;
- capture a particular soldier class;
- prepare for a Decisive Battle;
- test a weapon or Core family;
- replace losses;
- reach a trader or other point of interest.
A clear objective prevents two common mistakes: bringing an expensive squad to a low-value task, and continuing a dangerous run because you never defined what "enough" looked like.
Pre-departure checklist
1. Colony stability
Do not leave if removing the expedition squad will stop food, hauling, research or essential manufacturing. The colony continues to matter while the combat team is away.
2. Squad roles
A general squad needs:
- reliable ranged damage;
- at least one way to hold or redirect pressure;
- healing or recovery for longer engagements;
- area damage when infantry density is high;
- enough mobility or range to avoid every soldier clustering around the Leader.
Exact ratios depend on ship capacity and the classes you have captured. The role coverage matters more than copying a fixed number.
3. Equipment
Match the loadout to the expected target:
- Dense infantry: area damage, grenades, chaining or splash effects.
- Tanks and mechs: weak-point access, sustained damage and room to reposition.
- Long encounter: healing, shield support and ammunition reliability.
- Boss or elite capture: Capture Rounds, survivability and prison capacity.
- Unknown route: balanced ranged squad and flexible Core choices.
4. Replacement cost
Ask which deployed soldier would hurt most to lose. Rare support units and highly upgraded soldiers should not be exposed in the same way as replaceable frontline bodies.
Understand expedition escalation
Player reports and press observations describe enemy strength increasing as an expedition continues. Returning to base lowers that immediate pressure but gives up the current run's temporary Core build and expedition progress.
This produces a push-your-luck structure:
- early encounters are safer but provide fewer accumulated advantages;
- a coherent Core build makes the middle of a run powerful;
- rising enemy strength, injuries and bad positioning eventually reduce the margin for error;
- a strong build can tempt the player to stay after the squad has already become too fragile.
Do not judge danger only by the Leader's health. A run can be strategically lost before the player dies if medics, shield support or rare damage units are gone.
A practical return decision
Return when two or more of these are true:
- the expedition's original objective is complete;
- key support soldiers are dead, injured or repeatedly separated;
- the squad can no longer control ordinary encounters cleanly;
- your current build depends on a narrow interaction that fails against the next target;
- capture capacity, prison capacity or inventory value is already sufficient;
- one more loss would cost more than the likely reward;
- the colony has a research or production upgrade ready to turn the current haul into permanent power.
Continue when most of these are true:
- the squad remains intact;
- healing and shield recovery keep pace with incoming damage;
- the Core build has a clear and working identity;
- the next objective directly advances sector progress or a needed resource;
- you still have a safe exit plan;
- the colony does not urgently need the team or extracted materials.
This is a decision framework, not a hidden optimal percentage.
Squad control
Official descriptions confirm that you can order troops during battle. Community players commonly discuss F1 commands, close follow, loose follow and ordered positions.
Close follow
Use it when:
- entering a new area;
- moving through narrow terrain;
- escaping an ambush;
- keeping support units from drifting away.
Risk: tightly grouped soldiers are vulnerable to area attacks and may block one another.
Loose follow
Use it when:
- the battlefield has safe room to spread;
- ranged units need firing angles;
- area attacks punish clustering.
Risk: soldiers may chase or become separated, especially when AI behavior is inconsistent.
Hold or move to a position
Use it when:
- defending a controlled line;
- pulling enemies into ranged fire;
- keeping medics and shield support behind cover;
- preventing the squad from entering overlapping spawn zones.
Community reports describe Strike Force-heavy squads as effective at holding a position because they remain useful at range and can gain area-control tools as they improve.
Target priority
Use a simple order:
- threats that can disable or rapidly kill the squad;
- exposed high-damage enemies;
- targets controlling space with projectiles, missiles or artillery;
- durable frontline enemies;
- capture targets, once the battlefield is stable.
Do not stop dealing with active threats merely because a valuable enemy is ready to capture.
Weak points and vehicles
Official material emphasizes tanks, mechs and large mechanized battles. Player feedback identifies rear engine areas as important weak points on some tanks, but the exact damage multiplier has not been officially documented and may vary.
The strategic lesson is reliable:
- circle armored targets instead of trading damage from the front;
- use terrain to break projectile patterns;
- give the squad a position that does not force it to shoot into walls;
- check the battlefield for mounted or temporary anti-armor tools;
- remove nearby infantry before committing to a long weak-point attack.
Core timing and the return decision
Treat Core choices as a direction, not a collection, and let the phase of the run set the priority: early, a Core that works with the weapon already in your hands beats a theoretical late-game combo; mid-run, strengthen effects that are already producing results; before a major encounter, prefer one complete interaction over three unfinished ones; near the planned return, judge a Fragment by how many fights remain; do not take a dangerous detour to perfect a build you are about to reset.
The Core Fragments and Builds Guide owns the full selection rules: named archetypes, combination rules, and the pick sequence.
Squad templates by objective
These are starting templates built around expedition objectives, not a permanent tier ranking.
Safe progression squad
- one frontline or shield role;
- two or more healing sources when capacity allows;
- ranged generalists for consistent damage;
- one specialist chosen for the current objective.
Best for learning new sectors and protecting valuable soldiers.
Hold-position squad
- Strike Force or similar ranged generalists;
- Medics;
- a Shieldmaster where available;
- area damage from the Leader or Core build.
Community players report this style performing well when ordered to defend a good firing position.
Capture squad
- durable ranged damage that can stop shooting cleanly;
- healing and shield support;
- advanced Capture Rounds for elite or boss attempts;
- no uncontrolled damage effect that repeatedly kills weakened targets.
Remember that the Leader's melee attack can bypass AG-14's brief post-failure kill protection.
For which enemies are worth singling out, the soldier classes guide ranks capture targets by role; for what must be ready when the squad brings them home, the colony management guide covers prison capacity and processing.
Boss preparation squad
- enough support to survive a long phase;
- ranged damage able to attack while moving;
- area control for additional enemies;
- a coherent Core build rather than many unrelated effects.
For named encounters, check the Bosses and Sectors database before departure.
Common expedition mistakes
Filling every slot without checking roles
A large squad can still lack healing, range or area control. Build for coverage.
Letting support units lead
Move or hold the squad before the first enemy wave reaches the medics and shield units.
Chasing a capture during an unstable fight
First control the battlefield. A captured elite is not worth losing the expedition.
Keeping a good Core build for too long
Temporary power can hide permanent squad losses. Evaluate soldiers and objective progress separately from the excitement of the build.
Treating every encounter as an aim test
Position, weak points, squad commands and target priority can matter more than raw accuracy.
Returning after every small gain
Overly cautious play repeatedly resets run momentum. Set a useful objective, then return when the objective or risk framework says so.
Where the game requires thought
Expeditions are where Pax Autocratica is most strategic. You are simultaneously deciding:
- how much permanent value is already secured;
- how much temporary power the current build has accumulated;
- how replaceable each soldier is;
- whether the next fight fits the build;
- whether the colony benefits more from an immediate return.
The game does not require spreadsheet-level planning, but careless choices can turn a successful run into expensive recovery.
Sources and verification
- Official Steam store page: combat scale, squad orders, capture and Core families.
- Official Steam News feed: named encounters and balance changes.
- Directive AG-14: Capture Rounds, failed-capture protection and Core changes.
- Official Pax Autocratica subreddit: community-observed squad commands, escalation and class behavior.
- Developer launch AMA: developer description of combat and prisoners.
Verified Aug 26, 2026, against Directive AG-25. Return rules, command behavior and class-specific tactics remain community-observed unless the game or the developers explicitly document them.