Panludia
COMMUNITY INTEGRATION
Baldur's Gate 3Archipelago randomizer mod
Trade quest and battle checks for level fragments, equipment and optional gate unlocks. Release 0.7.2 revises container checks and the game bridge; new saves and careful story progression are essential.
Maintained by Broney / zane31415
- Reviewed build
- 0.7.2
- OS
- Windows
- Last reviewed
- 9 Oct 2026
- Installation
- Manual installation
How the game changes
- Quest milestones and selected battles send checks to your multiworld. Received Level Fragments replace natural levelling; equipment, supplies and optional gate unlocks change what your party can use and reach.
- Choose Rescue Halsin, Inquisitor Wwargaz, Myrkul or a custom boss list. Shorter goals use fewer acts and a lower expected level cap. Netherbrain and other Act III settings exist, but remain explicitly untested.
- The in-game window, opened with U, shows recent items, gate state and connection diagnostics. The dedicated BG3 client exchanges data with the host game through Script Extender files; the ordinary Text Client cannot deliver items.
- Version 0.7.2 revises Act I–II container data, removes several missable kill checks and adds optional container highlighting. Glowing containers are possible candidates, not a guarantee that each is an active check.
- Companion camp clothes can be shuffled. Optional traps include temporary status effects and hostile spawns; 0.7.2 replaces the minotaur spawn with a Meenlock. DeathLink, entrance barriers and class randomization remain optional.
Before you start
- Download both bg3.apworld and the Archipelago .pak from the same 0.7.2 release linked here. The separate mod repository still lists an older 0.7.1 package. Install Norbyte’s Script Extender, enable the PAK and start a new game. The APWorld declares Archipelago 0.6.2 or later; the PAK requires Script Extender 15.
- Generate the YAML and seed, then launch the dedicated Baldur's Gate 3 client or the generated .apbg3 file. Follow the setup guide for the initial sync scroll and Script Extender folder. U opens the in-game window; /resync in the client requests another item sync.
- Use the documented quest-based settings for a first run. Containersanity remains experimental even after the Act I–II revision; some highlighted containers are not checks. Act III coverage is unfinished, Statsanity is unimplemented, and companion class randomization is not recommended because starting attributes are not adapted.
- Keep separate saves before major quest transitions, including the grove and important Act II events. Branching quests, irreversible transitions and some kill outcomes can leave checks unavailable. A corrupt communication file can require restoring an earlier save to recover a one-time check.
- Keep one client for the host and one seed/slot associated with each save. The mod stores item history in the save, but does not enforce complete slot/seed isolation. Do not connect a different room or slot to an existing run as a way to test it.
- Avoid experience-table or creature-replacement mods, which can interfere with progression or check detection. Optional hostile-spawn traps and DeathLink can disrupt the party; several monster traps received together may produce only one spawn in the inspected build.
- The client permits unencrypted Archipelago connections, so use a trusted endpoint and enter any room password interactively. The tagged World matches the APWorld code; complete rebuild correspondence for the game PAK and a full compatibility matrix have not been established.
- The repositories provide MIT licences. The PAK also includes compiled game-story material; complete package notices and the scope of its redistribution permissions are not established by the reviewed evidence. This is a documentation limit, not a finding of unauthorized use.