Star Trek: ArmadaArchipelago randomizer mod

Compatibility notes

• Windows PC integration requiring your own retail Star Trek: Armada installation and Archipelago 0.6.7 or newer. Install the 0.6.7 APWorld, copy its observer DLL and injector beside Armada.exe, restart the AP Launcher and open Star Trek: Armada Client. The native files require the Microsoft Visual C++ runtime; compatibility with other game builds is not established.
• Version 0.6.7 enables GIVE_ALL_MISSIONS in ART_CFG.h before a new game process starts, keeping ART_CFG.h.archipelago-backup before its first change. The configuration remains enabled after play. Startup-intro skipping temporarily renames only STIntro.bik and has a next-client-launch recovery path.
• Campaign completions provide 20 checks; the default objective-transition option adds 47. The Mission Launcher shows received keys and locked missions. One starting faction is available initially; other factions and later missions require their shuffled access items.
• Finish The Alpha and the Omega, Part II. Keep the additional final mission completion requirement at its default zero: a higher threshold is enforced only by the client, outside World and Universal Tracker logic, and repeated mission results count toward it.
• Campaign keys and mission access are implemented. Capability and Dilithium Supply Cache items are recorded but currently have no game effect; this build does not implement unit, research or resource randomization. Optional Nebula Anomaly traps default to zero and have timed removal handlers, but dispatch confirmation does not establish that the effect completed.
• Use one room/slot per Windows user profile and back up both game saves and the client journal before changing rooms. The journal is shared rather than seed/slot isolated; offline events and checks sent around a disconnect are not guaranteed to be recovered. Stay connected for mission completions and unique objectives.
• For an internet room, use its supported wss:// address where available and keep credentials out of connection URLs and shared logs. Complete redistribution notices and icon provenance were not supplied in this package. These are documentation and static robustness limits; no played-session compatibility is claimed.