You Have to Win the GameArchipelago randomizer mod

Compatibility notes

• Use the Windows Steam edition, APWorld 1.1.0 and game.mods.zip from the same release. The APWorld manifest requires Archipelago 0.6.7 or newer. The included YAML template still declares game version 1.0.1, matching the tagged source manifest rather than the released APWorld manifest; confirm the version pairing in the generated setup. The client uses fixed offsets in the 32-bit Windows executable; native Linux/macOS editions and other game builds are not established here.
• Back up the game-specific Documents/My Games folder before copying the Maps and Mods contents. Install the APWorld, prepare the supplied player YAML and generate a room, then start a new Archipelago campaign and open the game client from the Archipelago Launcher.
• Default multiworld settings have a generation-capacity conflict: Local Nothing Percentage reserves too many locations for the remaining item pool. Lower that setting or add optional room/bell checks, then confirm generation succeeds. The single-player branch does not apply this local-filler reservation.
• Keep Password Randomization Off for the simplest setup. The Any mode stores the generated password as a list, while the client compares it with text; its success route is not coherent. Words mode uses text, but neither randomized mode has supplied regression tests.
• Keep the client connected before exploring rooms or ringing bells. Optional room and checkpoint checks are observed from the current state, not replayed from a persistent visit history. Treasure rescans also depend on a changed pickup count.
• Use a separate save for each room and fully restart both game and client before switching seeds or saves. The save counter is not bound to a seed or slot, and in-memory letters and unlock flags are not fully reset between connections.
• The crouch warp defaults to about 2.5 seconds of normal polling and is disabled inside secret-room traps. The overview still says about five seconds. Trap effects, game closure and loading transitions have incomplete cleanup; keep backups and leave traps off for a simpler run.
• Check important pickups and victory on the server after a connection interruption. Process loss can stop the watcher without automatic recovery. The client has no executed tests here establishing crash-safe item delivery or reliable resumption.
• Avoid putting credentials in the server-address URL: the required core can log and remember it. Use an explicit wss:// address when supported by your server; a bare host uses plain transport.