Zork: Grand InquisitorArchipelago randomizer mod

Compatibility notes

• Version 3.0.0 is incompatible with games generated in earlier versions. Generate a new room/seed and start a new game. Keep backups of existing saves; updating the APWorld does not convert a 2.x run.
• Use Windows, Archipelago 0.6.7 or newer, and the exact Windows 64-bit ScummVM 2026.3.0 build linked in the setup guide. The client accesses that process through Win32 and verifies its engine signature. Native Linux and Wine compatibility are not established by this release guide.
• For Steam, extract the specified ScummVM build into a separate folder and use Add Game to select the installed game. Keep your own game copy and back up any installation you change. The old manual audio-file workaround is superseded by this client release.
• Install the APWorld on the generator and your Archipelago client installation, prepare the player YAML and generate a room. Launch the game, pass the opening cinematic, open Zork Grand Inquisitor Client, connect with the room and slot, then run /zork. Cast VOXAM from its quickbar shortcut.
• Fully close and restart ScummVM whenever you update the APWorld. The client installs an engine interface in the running process; replacing only the client file can leave the previous interface loaded.
• Resume the save associated with the same slot. The client checks save identifiers, but this does not guarantee atomic recovery after an interrupted write. Stop playing whenever attachment is lost and use /zork again after restarting the game.
• Stay connected while completing unique actions. The inspected client removes checks from its send queue before acknowledgement, and goal transmission is latched without a confirmed receipt. After a disconnect, confirm important checks and victory on the room rather than assuming every action replayed.
• Universal Tracker is strongly recommended and required for reachable-check display and optional missable assistance. Leave traps and complicated route shuffles disabled for a simpler first run. Deathsanity records distinct game deaths; it is separate from DeathLink.
• Avoid embedding credentials in the server-address URL because framework logs and remembered addresses can retain it. Use an explicit wss:// address when your server supports it. The ordinary bare-host setup uses unencrypted transport.