Panludia
COMMUNITY INTEGRATION
Star Trek: Armada IIArchipelago randomizer mod
Play individually unlocked Federation, Klingon and Borg campaign missions. Completed objectives and first eligible local builds send multiworld rewards, while persistent upgrades, caches and timed traps affect the current local team. Win Rifts to complete the slot.
Maintained by reedwhaley
- Reviewed build
- 0.1.0
- OS
- Windows
- Last reviewed
- 13 Oct 2026
- Installation
- Manual installation
How the game changes
- 301 shuffled rewards across 29 ordinary mission completions, 125 objectives and 147 faction/build types. The final Rifts completion is locked Victory.
- Mission access and faction keys unlock the campaign launcher; the starting faction’s first mission and key are precollected. Rifts needs Fluidic Space and all three faction keys.
- Five permanent upgrades have twenty 5% steps each; caches, targeted repairs, temporary speed changes and eight trap effects support the local team.
- Trap Count is 72 by default and can be reduced to zero; omitted copies become positive helpful effects. An optional client counter requires up to 29 other mission completions before Rifts.
Before you start
- Install the 0.1.0 APWorld in Archipelago 0.6.7 or newer. Copy the matching observer and injector beside Armada2.exe and select that game folder in the client.
- The delivered observer embeds one accepted executable SHA-256. A different game binary is not established as compatible. Source paths and package integrity were inspected; native game execution and full binary reconstruction were not performed.
- Other mission completion requirement is enforced by the client launcher but is absent from the World’s final access rule. Borg Mission 10 Access is generated but does not unlock Rifts.
- Helpful and trap receipts are marked dispatched after the native adapter queues them. A later target rejection is not equivalent to a successful gameplay effect and is not retried by that path.
- Objective rewards can be reconciled at mission victory. First builds require their eligible mission and a local-player queue completion; winning does not infer builds that were never recorded.
- During managed launches the client temporarily renames four application startup videos and restores them after its owned process ends. Mission briefings and cinematics remain.