Pax Autocratica Guides

Pax Autocratica Guides

Start Pax Autocratica with the correct Steam product, a practical colony-to-expedition plan, and clear Early Access boundaries.

3 guides
3 start here
Guides guide hub
ProductSteam base game AppID 1067360; related Demo, Prologue, and Playtest apps identified separately VersionEarly Access public branch; status checked 2026-08-15 after Directive AG-14 PlatformNative Windows; Steam lists Single-player, Full Controller Support, Steam Cloud, and Save Anytime

Pax Autocratica is an Early Access colony simulation and first-person roguelite played through Steam AppID 1067360. You develop a settlement, assign citizens to work, produce equipment and supplies, then take soldiers into expeditions that return resources and captives to the colony. The safest way to begin is to treat those two halves as one loop: prepare the colony before leaving, pursue one expedition goal, return before shortages become difficult to diagnose, and process the results before starting another run.

Current product: the playable base game entered Early Access on August 10, 2026. Old Demo, Prologue, and Playtest listings are separate product records and should not be used as authority for current balance or progression.

Pick the answer you need first

Understand the colony-to-expedition rhythm

Begin in the colony long enough to learn what is already running and what is blocked. Open the current objectives, inspect the buildings that are damaged or unavailable, and look at the citizens actually assigned to gathering, hauling, research, food, and manufacturing. A building with inputs but no output may lack a worker, a delivery, power, research, or a completed repair; guessing at a new construction rarely fixes all five possibilities.

Before an expedition, choose one purpose. You might need a resource, another captive, progress on the Star Map, or a mission result. Empty or organize the Leader’s inventory, review troop deployment, confirm ammunition and healing, and save. The game officially supports saving at any time, including during expeditions, but keeping a clear pre-departure save makes experimentation easier to undo.

While you are away, assigned citizens continue living and working in the colony. That makes automation valuable, but it also means a weak food or hauling chain can deteriorate while combat has your attention. Return with enough time to unload materials, resolve prisoners, replace losses, and read new research or mission prompts. Starting another expedition immediately can bury the reason a production line stopped.

Use a first-session sequence that teaches causes

Moment
Action
Useful result
Arrival
Read objectives and inspect damaged core structures before placing extras.
You know which repairs and unlocks control the opening.
Workforce
Match a small number of citizens to visible jobs and watch one full delivery cycle.
You can tell assignment trouble from hauling trouble.
Production
Secure immediate food, gathering, storage, research, and the supplies required by the next objective.
The colony can function while you enter combat.
Expedition
Lower difficulty if necessary, keep the squad visible, and learn one battlefield objective.
You return with information as well as loot.
Debrief
Unload, review casualties and captives, then revisit research and missions.
Each run produces a deliberate next step.

This order is not a speedrun route. It is a diagnostic route. By changing one part of the settlement at a time, you see why a resource began moving or why a citizen stopped. By pursuing one battlefield purpose, you can distinguish mission progress from incidental pickups.

Read people as individuals, not identical labor slots

Citizens and soldiers carry attributes, traits, needs, relationships, and changing states. The official game description highlights fear, loyalty, bonds, feuds, rebellion, work, capture, and conversion. That means a vacancy is not solved only by adding another body. Look at whether the candidate fits the job, whether stamina and schedule permit useful work, and whether current conditions are producing hunger, fear, unhappiness, or disloyalty.

For soldiers, work traits and battle traits answer different questions. A valuable colony worker may be a poor fit for the next expedition, while an elite captive can arrive with random attributes or affixes that make careful inspection worthwhile. Do not sacrifice, exile, upgrade, or convert someone solely because of color or rarity before reading the complete panel and understanding the cost. Early Access patches have already adjusted soldier upgrade progression and added an aging toggle, so inherited advice can become wrong quickly.

Treat Early Access notices as operating conditions

Directive AG-12 added automatic save backups, a Soldier Aging toggle, soldier exile, manual deposit quantities, and several progression changes. Directive AG-14 added three advanced Capture Rounds, changed capture-failure protection, improved 16:10 deployment UI, and fixed issues involving hauling, Trade Port prices, Mandatory Reproduction, and other systems. These are meaningful changes to everyday play, not merely background news.

When a mechanic behaves differently from an older video, prefer the current interface and the latest official announcement. Record the date and branch when sharing a workaround. A BuildID visible through third-party telemetry is not the public version name; Multiverse had not published a semantic version label as of August 15. Use announcement titles and dates instead of inventing a numbered release.

Avoid the most common product and feature mix-ups

The retired Demo AppID 1069590, the separate Pax Autocratica: Prologue AppID 4107120, the historical base-game Playtest AppID 2194080, and the Prologue Playtest AppID 4150700 are not interchangeable with the current base game. A tutorial step, balance value, availability claim, or save behavior captured in one of those products needs confirmation in AppID 1067360 before it guides a current player.

Steam currently labels the base game Single-player. The developer has discussed co-op as a major feature hoped for during Early Access and lists it among work or investigation, but no live mode or reliable release date was announced by the check date. Do not buy a second copy expecting immediate co-op. Likewise, a Steam key is a store license, not an in-game redemption code; no supported code-redemption system is documented.

Recover cleanly when the opening becomes confusing

If progression stops, pause expansion and identify the exact symptom. For a colony issue, follow one resource from source to storage to destination and inspect the assigned worker. For a mission issue, read the active objective and look for a prerequisite repair, interaction, research item, or Star Map state. For a battle failure, lower the difficulty, shorten the squad order, and learn the objective rather than spending every reserve on another uncontrolled attempt.

For crashes, freezes, or loading trouble, Multiverse currently recommends verifying Steam files, turning off DLSS Super Resolution, and turning off Frame Generation before reporting the issue with logs and save data. Preserve the automatic backup and a manual save before resetting settings. These reversible steps keep a technical problem from becoming a lost colony.

Sources checked August 15, 2026

Recommended guides

Choose the guide that matches what you want to do next.

All Guides guides

3 focused guides with steps, checks, and current caveats.