Welcome to the Hangar Open Beta. Please report any issue you encounter on GitHub!
Your server on HTTP: REST and WebSocket for sites, bots, and AI agents, with tokens, scopes, and an audit log.
A security release that takes something away from moderators: making operators now needs server:console.
Security
- 🔒 Moderators could reach every permission.
players:moderate, which the defaultmoderatorgroup has, could make any player an operator. An operator may run/worldapi, which makes tokens and panel codes with any permission,codeandfiles:writeamong them. Making or unmaking operators now needsserver:console, which onlyadminandownerhave by default:PATCH /server/ops,PATCH /players/{player}/permissions, and writingops.jsonthrough/files. - 🔒 WorldAPI's own permissions stay out of the API.
POST /server/commandsrefuses any command that names aworldapi.*node, such aslp user Steve permission set worldapi.admin true, with 403protected_permission, whatever the token holds. Change those permissions in game or in your permissions plugin.
What changes for moderators
- A
moderatortoken or account can no longer make or unmake operators; it gets 403missing_scope. Kicks, bans, the whitelist, and reading the operator list stay as they were. Giveserver:consoleon purpose to anyone who should make operators, knowing it reaches as far asowner. - The panel shows the operator button on a player's page only to accounts with
server:console.
Platforms
Paper
26.3