Skip to content

Latchkey 0.3.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 06:06
· 19 commits to main since this release
e47acff

The lobby: where arriving players start, with a welcome for first-timers and events other plugins can use. Works with or without Multiverse or Waystation.

Needs

  • Paper 26.1 or later and Java 25.
  • Everything 0.2.0 needed for invites and sign-in. The lobby needs only a loaded world.

New in 0.3.0

  • The lobby. Set lobby.world (and optionally lobby.spawn) and arriving players start there. lobby.send is first-join by default, or always or never. First-timers get a title and chat lines from lobby.welcome. Who is new comes from the server's own record, so nothing more about players is stored. If the world isn't loaded, nobody is sent anywhere and the console says how to fix it. These defaults are the owner's decision of 2026-11-10.
  • For other plugins. FirstJoinEvent, PlayerArrivedEvent on every join, and lobbyLocation(), read by name with no dependency. Waystation 0.5.0 uses them for its lobby gate.
  • Lists in pages. /latchkey invite list --json answers {"items": [...], "next": ...}, the shared Signalbox format, with limit and cursor. Signalbox 0.3.0 is inside the jar.
  • describe marks optional arguments.

Upgrading from 0.2.0

Replace the jar and restart. The lobby stays off until you set lobby.world, so nothing changes until you do. Leaf Juice or scripts that read invite list --json should read items instead of invites.

Tested

193 unit and HTTP tests. The bot test passes 44/44 on throwaway Paper 26.1.2 and 26.3 servers with Usher 0.4.1: a first join sent to the lobby spot and welcomed, a returning player left where they were, and a profile made unsafe after its invite refused at use. Waystation's arrival suite used this jar for its lobby gate, 29/29 on 26.3.

Not tried: a real game client (the lobby title can't be seen by a bot), HTTPS through a real tunnel, or a real server.