JigsawArchipelago randomizer mod

Playing with others

Play separate puzzles in separate Archipelago slots, or share a slot and synchronize its puzzle through the server. Live exchanges and returning to an available asynchronous room use the same connection. Local solo practice is separate from a generated multiworld.

Known scope and limitations

• Install the published 0.10.0 APWorld on the room generator with Archipelago 0.6.0 or later. Create one YAML per puzzle and generate locally: the Archipelago website cannot generate this custom World. The host can upload the resulting ZIP there to host the room. Players then use the author's HTTPS browser client with the room address and exact slot name.
• Avoid Jigsaw AutoLaunch and password-bearing shared links. The bundled automatic launcher constructs an HTTP URL containing connection credentials. Enter the password directly into the HTTPS form instead; the reviewed form remembers host and name, not the password in local storage.
• The default website and the newer beta website are separate clients. Version 0.10.0 release notes advertise GIFs, camera input, browser capture and an accelerated renderer for the beta. The default site still links that beta with a performance warning; these features are not promised for both clients.
• The 2,500-piece figure in the release notes applies to solo play on the beta site, not the APWorld's 2,000-piece option. Start with a small puzzle before choosing a large grid, many rotations or fake pieces.
• Online piece positions, merged groups and merge count are stored on the Archipelago server under the slot. The image is kept separately in browser IndexedDB using seed and slot. Clearing browser data can remove a custom image even when the server still has puzzle progress.
• Default pictures load from external image providers. Use an image you trust and have permission to use. When reopening a shared puzzle, retain the same image aspect ratio or saved positions may no longer line up as expected.
• Keep the server connection active. On disconnection the client asks for a refresh; this review does not establish durable offline check delivery or atomic recovery of every merge and goal during an interrupted save.
• Same-slot piece synchronization is implemented through server storage and bounce messages. That does not establish conflict-free editing at arbitrary player counts. The browser's separate fixed-seed solo practice explicitly has no save.
• Use conservative trap settings for a first room. This review covers published options, generation and selected browser connection, storage and check paths, not a completed multiplayer puzzle or a security certification of either hosted client.