MindustryArchipelago randomizer mod

Playing with others

Separate campaigns can participate in a multiworld and reconnect later. Native network campaign hosting exists, but guest reward ownership across multiple AP slots is not fully documented. Shared-campaign behavior is not independently certified by Panludia.

Known scope and limitations

• This is a separate open-source game fork, not a plugin for the current Steam executable. Extract it into its own directory. It uses a v146-era foundation; do not assume newer vanilla content, Steam features or unrelated mods carry over.
• The maintainer explicitly pairs client 0.5.1 with APWorld 0.5.0. Windows has a packaged executable; Linux uses the supplied Java client and Java 17 setup. macOS is not listed just because vanilla Mindustry supports it.
• Keep Military Level Tracking enabled for a conservative run. Disabling it can place needed turrets or units behind sectors the player cannot reasonably clear. Randomized starting weapons can also radically change balance.
• A public co-op report describes incorrect weapon visuals for guests when core-unit weapon randomization is enabled. The host's weapon behavior wins; leave that optional randomization off when sharing a campaign.
• A newly unlocked technology category may not appear in the build menu until you leave and re-enter the sector or receive another item.
• Research-discount filler allocation is explicitly provisional. For a conservative first seed, leave it off. Faster unit production also benefits enemies, and core-level DeathLink can lose an entire sector.
• AP and vanilla saves are separate, but backups remain advisable. Reset AP Data erases this client's campaign and research for a new multiworld. The APWorld lacks a manifest, so future Archipelago 0.7 compatibility is not established.