Combat

Pax Autocratica Weapon Cores Guide

Choose Pax Autocratica weapon cores by combat job, test them safely, account for area effects and capture risk, and record the current Directive version.

Weapon cores in Pax Autocratica should be evaluated as tools for a squad job. Current patch notes name Vortex Shell, Thunderbolt Arrow, and Toxic Fog Core, but they do not provide a complete fixed tier list or every internal number. Read the current tooltip, test the delivery in a controlled encounter, and judge whether it makes the intended mission more reliable.

Start with the attack you need

Name the battlefield problem first: concentrated damage, an area response, capture-safe pressure, distance, or support for a particular soldier. A core that excels against clustered enemies can be the wrong answer beside a prisoner candidate. A focused option may look weaker in a general damage test and still be the safer mission tool.

Check what the colony can manufacture and replace. One impressive core does not create a repeatable build if the required production empties reserves needed for repairs, food, or another squad. Include material flow in the build decision.

Read current evidence correctly

Directive AG-14 says Vortex Shell damage was increased and Thunderbolt Arrow received a larger area. Those are confirmed directions of change on the August 15 public branch. The note does not establish their final relative rank, every target interaction, or the exact value shown in later patches.

AG-10/11 era fixes also referenced Toxic Fog Core against the Tree of Asherah. Treat that as encounter-specific patch history, not proof that the core is universally best or worst. Verify whether the behavior you care about still reproduces before preserving a workaround.

Run a controlled field test

Observation
Keep constant
What it answers
Delivery
User, weapon, and target type
Whether the effect reaches the intended enemy reliably
Coverage
Enemy spacing and camera position
How many targets the current area can affect
Control
Command order and encounter opening
Whether the attack can stop when priorities change
Cost
Mission length and production state
Whether the colony can sustain repeated deployments

Use an ordinary sector where retreat is possible, make a manual save, and change one core at a time. Record the Directive date with the result. A test that changes weapon, soldier, formation, and enemy group simultaneously cannot isolate what the core contributed.

Account for area and target discipline

Area effects reward enemy clustering, but they also reduce control around a capture target. If capture is part of the mission, separate the intended prisoner before activating a wide effect and stop soldiers whose normal behavior keeps applying damage. The Leader’s melee can bypass AG-14’s temporary protection after a failed capture, so core selection does not remove the need for command discipline.

Against a boss, area size may matter less than reliable contact with the actual vulnerable target or associated objects. Read the encounter indicator and observe the result rather than assuming that a larger area automatically connects with every mechanic.

Match the core to the squad

Focused mission

Favor predictable delivery and the ability to stop damage when one target matters.

Crowd pressure

Consider coverage and positioning, then confirm the expanded effect does not expose the squad.

Long expedition

Compare repeatability and production cost rather than one dramatic hit.

Boss attempt

Fit the active mechanic and target window; keep a stable fallback when the preferred effect misses.

The citizen using the weapon matters as much as the core. Condition, role, positioning, and command response decide whether an effect is delivered at the right time. Test the whole assigned job, then keep the parts that remain dependable.

Update a build after a Directive

When patch notes change a named core, do not discard or celebrate the build immediately. Re-run the same small encounter and compare delivery, coverage, and resource use. If the live tooltip changed, record the new description; if only behavior changed, keep the observation tied to the branch and date.

Avoid importing lists from a Demo, Prologue, Playtest, or unrelated Steam application. This guide is scoped only to base AppID 1067360. Separate product identities can have different content or balance even when the title and visuals are similar.

Fix a core that appears ineffective

Confirm the core is installed or supplied to the intended weapon and soldier. Check that the target is valid and reachable, that another command is not overriding the attack, and that the effect is not being judged against an immune or special encounter state. Repeat once in a simpler fight.

If behavior remains reproducibly wrong, preserve the save, note the exact core, user, sector, Directive version, and steps, then use the official support community. Return to the Combat hub for squad roles and mission planning before changing every item in the loadout.

Sources checked August 15, 2026

Continue with another focused Pax Autocratica guide.

Combat

Pax Autocratica Builds

Create a Pax Autocratica player build around one mission job, then test weapons, cores, range, control, capture safety, and patch-sensitive tradeoffs.

Combat

Pax Autocratica Combat Guide

Learn Pax Autocratica combat through threat reading, controlled movement, squad roles, weapon-core testing, capture restraint, and safe recovery.

Combat

Pax Autocratica Squad Builds

Assemble a Pax Autocratica squad by mission roles, command visibility, colony opportunity cost, capture discipline, and recoverable losses.