Repository navigation
Latchkey 0.4.0
The invite page becomes one box, and a player who uses their invite gets a welcome page with the address to join.
Changes
- Code only. The page asks for the invite code alone. A code that matches an open invite shows "This invite is for " and uses nothing up; "Yes, that's me" uses it, puts the player on the whitelist and signs that browser in. No Microsoft sign-in, ever: the server checks the account the first time they join. (Owner's choices, 2026-11-10.)
- The welcome view. A signed-in browser sees the server's logo and name, the address to join (with a copy button), and first steps. All of it is set under
page:inconfig.yml. The address is never in a page anyone can open: only in this view, served withCache-Control: no-store. - A logo, read only from
plugins/Latchkey/, PNG or WebP by its own bytes, at most 512 KB. - HTTPS with Caddy. docs/https-with-caddy.md explains putting Caddy in front of a playit HTTPS tunnel, and the trust boundary that keeps per-visitor rate limits working.
Upgrading
Replace the jar and restart. config.yml gains a page: section; until you fill it in, the page shows "Join the server" and two general first steps. Anything that read the old two-field form (code and username) must send the code alone and then confirm.
Tested
204 unit and HTTP tests, 11 new: the play address is absent from every answer to a browser that isn't signed in (the code page, the "This invite is for…" page, errors, 404s, wrong methods, sign-out, the logo) and present after the invite is used; looking at an invite uses nothing up; eight browsers racing one confirm get one admission; the logo checks. The bot test with Usher 0.4.1 passed 45/45 on Paper 26.1.2. Not tried yet: HTTPS through playit and Caddy, a real browser, a real client.
Also in 0.4.0
- Open the map. A signed-in browser can be handed to the map once, with a one-time link that works for a minute. The map checks the whitelist and bans when it takes the hand-off and again while it's open. It's for Mapkeeper.
- The playit preset.
/latchkey tunnelprints the tunnel settings, anddocs/has a ready Caddyfile matched to the tunnel's ports, with the map host. - A health check from outside, and the landing page's own paths are reserved.
- An internal failure gets the plain error page.
- Rewild is told what Latchkey owns, so it's never rewilded.
Tested on a copy of a real server
On an APFS copy of a real server (2026-11-14), on Paper 26.2 and then 26.3 build 249, with bots: the plugin loads and its checks pass. On 26.3 the bots can't walk (ViaVersion clients are refused for moving), so checks that need walking ran on 26.2 only.