Actions
Action scopes let an app do something as the player — like sending a gang message. The server verifies the live player and their relationships before every action, then audits the result.
How an action is authorized
The app requests an action
Your mod or backend asks to perform a write, like sending a message to gang chat.
The server verifies the live player
The action is bound to the real player from the live Minecraft connection — never a player id sent in a client packet.
The server verifies relationships
Membership and ownership are re-checked on that server, so a gang message can only be sent to the player's current gang.
The action runs, or nothing happens
Only a passing action is performed. Failed checks send nothing, are audited, and players can revoke the grant at any time.
Action scopes
Show prompts
ui.prompt:writeSensitiveShow an in-game prompt that you can answer.
Send gang messages
gang.messages:writeSensitiveSend messages from you to your current gang chat. The server checks your live player and gang before every message.
Send gang pings
gang.ping:writeSensitiveSend a location ping to your current gang.
Send telemetry
telemetry:writeSend anonymous usage telemetry for your app.
Rate limits
Writes are rate limited
Action scopes are rate limited per player, app, gang, and server. For gang messages the target is at least one accepted message per second, with stricter burst controls to prevent spam. Rejected writes send nothing and are audited.
Relationship bypass
Backend apps only
Relationship bypass lets an approved backend or hybrid app act without the per-request relationship check. It is never available to client mods, requires an explicit reason and admin approval, and is shown with a warning wherever you select it.