Pax Autocratica officially includes weapon cores and combination cores. The public store does not expose a complete current catalog, while Directive AG-14 shows that individual core effects are already being balanced. This list is a verification-first index: read the exact entity in the base-game public branch, then record what it actually changes.
Separate core identity from the host weapon
Copy the exact displayed core name, type, description, compatibility, trigger, affected target or area, source, and current directive. Record the host weapon separately. Otherwise a weapon’s ordinary behavior can be mistaken for the installed core, or a combined effect can be assigned to a single component.
Remove or swap only one core during a controlled test. If the interface prevents an isolated test, mark the observed combination honestly.
Use a consistent effect record
Track officially named changed cores
Directive AG-14 names Vortex Shell and Thunderbolt Arrow in its balance changes. That first-party evidence confirms those names are relevant to the current base game and that advice involving them needs an August 15 recheck. The directive should not be stretched into unsupported exact damage, radius, cooldown, rarity, or source claims.
For each, read the current in-game description and record the installed context before testing. If an older note conflicts with the public branch, keep the old result as historical rather than merging values.
Vortex Shell
Confirmed as changed in AG-14. Re-read current behavior, coverage, and compatible setup before reusing an earlier build.
Thunderbolt Arrow
Confirmed as changed in AG-14. Retest its area behavior and tactical role without inventing values absent from the live text.
Other observed cores
Add only exact names seen in the current base game, with one verified source and host context.
Combination result
Describe the tested pairing separately so a combined outcome is not attributed to either core alone.
Distinguish the index from build advice
This page answers what a core is called, where it was observed, what the current text says, how it triggers, and what it affected. Weapon Cores explains how to evaluate synergy, while Builds turns that evidence into a mission-specific loadout.
Keeping the boundary matters for search and maintenance. A factual entry can remain useful after a strategy changes, while a strategy needs difficulty, mission, weapon, and squad context.
Reverify after every relevant directive
Flag entries named by an official update. Reopen the inventory, copy the new description, and repeat the smallest isolated test. Preserve the previous date rather than silently replacing history. If a core vanishes or changes name, record the current absence only for the branch you checked.
For a trigger-based core, store one positive and one negative observation. The positive case shows the action that activated it; the negative case shows a similar action that did not. For area or movement effects, include the starting position and target arrangement. This separates a real trigger from coincidental battlefield activity.
Combination cores need a relationship record. Name every installed component, the host weapon, the order or interface used to combine them, and the resulting description. If the game presents a new combined entity, index that result separately while linking the ingredients. This preserves the difference between component facts and emergent build behavior.
Do not fill gaps with a fan-made “complete” list or legacy EFAS data. The correct index can be incomplete while Early Access evidence is sparse; fabricated completeness is harder for players to detect and maintain.
Sources checked August 15, 2026
- Pax Autocratica on Steam — official weapon-core and combination-core scope.
- Official Steam News — AG-14 references to Vortex Shell and Thunderbolt Arrow.