On Fabric, the only system provided is Minecraft's op permissions system. Because of that, PermissionsEx provides all of its own integrations with Minecraft itself, and some other mods. We are happy to work with other mods to implement permissions checks as well -- feel free to pop into our Discord.
We aim to replace every op check in vanilla (i.e. unmodded) Minecraft with a permissions check. To that end, we provide the following permissions:
Permission | Purpose |
| Use the command |
| Allow users to log in to a whitelisted server without being whitelisted |
| Allow users to build within the spawn protection radius |
| Allow users to log in even when the server has reached its player limit |
| Bypass the "Player moved too fast" limit |
| Bypass the "Player moved too fast" kick when in a vehicle |
| Bypass the kick for sending chat messages faster than allowed by the game |
| Allow setting the game's difficulty |
| Allow placing/editing/viewing/breaking a command block, jigsaw block, or structure block depending on which permissions are given |
| Allow using the debug stick on the |
| Allow placing blocks or entities while preserving their NBT data ( |
| Allow using selectors in commands |
| Allow sending admin broadcasts to other players |
| Receive messages sent to "ops" from command output |
Players are represented as users
The server console is represented as the subject system:Console
Command blocks are represented as commandblock:<name>, where the default command block name is @
Sign representation has not been decided yet
RCON connections are represented as system:Recon (Yes, that is Recon -- that's what the Rcon command source is named internally.)
Functions executed through tags #minecraft:tick and #minecraft:load tags are represented as function:minecraft:tick and function:minecraft:load respectively
NOTE: functions currently only perform permissions checks when they're loaded, not on individual executions. This needs to be resolved for function permissions to actually be useful.
Context Key | Example Value | Description |
|
| The identifier of a dimension a subject is currently in |
|
| The identifier of the type of dimension a subject is in |
|
| The IP address a subject is connecting from |
|
| The hostname a client is connecting to the server with |
|
| The ip (on the server) that is receiving the connection from a subject |
|
| The port (on the server) that the client is connecting to |
|
| The function currently executing. When nested functions are in progress, multiple values will be specified. |
We provide a permission resolver for WorldEdit so its commands check PermissionsEx for permissions
PEX provides a significant level of integration into Fabric. This provides some details on what we look for when trying to provide permissions checks
ServerCommandSource.hasPermissionLevel
Entity.allowsPermissionLevel
Entity.getPermissionLevel
PlayerEntity.isCreativeLevelTwoOp
ServerPlayNetworkHandler.isServerOwner
MinecraftServer.isOwner
MinecraftServer.getPermissionLevel
PlayerManager.isOperator
PlayerManager.areCheatsAllowed
PlayerManager.getOpList
PlayerManager.getOpNames
OperatorList.get
Broadcast to ops should have the subject type of the source in the permission somehow
Check whether we enforce creative mode for certain items (debug stick, etc)
Changing permissions is very slow -- investigate this
F3 Debug toggle creative/spectator
Debug stick and other technical blocks