Air DeliveryArchipelago randomizer mod

Compatibility notes

• Use air_delivery.apworld and the dedicated client from release 0.1.6, not the unmodified Lexaloffle cartridge. The release guide allows opening the extracted client's index.html in a browser; the author also hosts a playable client.
• The author states that the APWorld's hidden auto-launch component needs Archipelago newer than 0.5.0. The published archive has no archipelago.json manifest; future Archipelago compatibility is not guaranteed by its release number.
• Enter the room host, port, exact slot name and optional password. The hosted client now exposes the password field added in 0.1.6, despite the release's earlier warning that the website update might be delayed. Hosted bytes can change separately from a tagged download.
• Reset the game before switching slots: the guide warns that inventory and sent locations otherwise carry over. Reconnecting can replay received item flags, but this review does not establish durable restoration of the full game state after closing the page. Stay connected while collecting checks.
• Do not put a room password in a shared URL. Auto-launch and optional connection parameters can include credentials in the address, browser history or logs. Enter it in the password field instead and use a trusted room.
• The downloaded page still loads archipelago.js 2.0.2 from unpkg.com. It is not a fully offline package. The bundled optional host.py listens on all interfaces at port 80; it is not required by the documented open-index.html route and should not be exposed to other networks.
• Source review found that the Friend Freight alternative-route rule closes over its last alternative, so generation can require Fly even where Claw works in the game. Treat the published logic as more restrictive at that check, not as a physical barrier. No independent full playthrough was performed.
• Version 0.1.6 fixes an unnecessary Claw requirement around the key-door route. A remaining suggestion asks for more claw-less sequence-break logic. Browser chat renders text rather than interpreting it as HTML, but its message history grows without a visible cap; very long busy sessions may become heavier.