Minecraft:Permission level
More actions
Permission level is used to describe the permissions a player or a command executor has.
For example, in Template:Editions,
- REDIRECT Template:Command
Template:Redr can't be executed in a command block, because this command requires the executor to have a permission level of 3, while command blocks have a permission level of only 2.
Description
Levels are incremental, meaning level n allows anything that any level less than n allows.
Java Edition
in Template:Editions, the permission levels may allow players to configure certain game settings:
Level 0 – Operator
- The player can enable the TPS graph in the debug screen.
- The player can see command block output in chat, if the game rule is enabled.
- The player can see command output from other operators and the server console if
broadcast-console-to-opsis enabled.
Level 1 – Moderator
- The player can bypass spawn protection.
Level 2 – Gamemaster
- More commands are available.
- The player can use command blocks.
- The player can copy the server-side NBT data of an entity or a block entity when pressing the
- REDIRECT Template:Keys
Template:Redr debug hotkey, and copy the client-side NBT data when pressing
- REDIRECT Template:Keys
- The player can use
- REDIRECT Template:Keys
Template:Redr (game mode switcher) and
- REDIRECT Template:Keys
Template:Redr debug hotkey (toggle between Spectator and the previous game mode).
- The player can change or lock difficulty in Options screen. Note that the player in a singleplayer world or the owner of a LAN world can change or lock difficulty without a permission level of 2.
- With "Operator Items Tab" option turned on, the player can find operator items and an "Operator Utilities" tab in the Minecraft:creative inventory.
- Target selectors can be used in commands like
- REDIRECT Template:Command
Template:Redr and raw JSON texts.
Level 3 – Admin
- Commands related to multiplayer management are available.
Level 4 – Owner
- All commands are available, including commands related to server management.
Bedrock Edition
in Template:Editions, permission levels mostly dictate which commands a player may use. In different levels, certain commands are available, and a level inherits commands from levels less than it.
The permission levels and their available commands are:Template:Note
Level 0 – Any / Normal
All commands available to non-privileged players:
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
Level 1 – Game Directors / Operator
Mostly commands that affect gameplay and entities: Template:Collapse
Level 2 – Admin / Host
Server operator commands:
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
Level 3 – Host / Automation
Server host commands:
- REDIRECT Template:Command
Level 4 – Owner / Admin
Server administrator commands:
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
- REDIRECT Template:Command
Player Permissions
Script error: No such module "Exclusive".
<section begin="player-permissions"/>
Player permissions dictate what the player can and cannot do in a multiplayer game. For example, actions such as building, mining, attacking mobs or players can be disabled or restricted by each of their own permissions. They can be configured individually or by preset roles on a separate screen accessible in the pause menu.
There are four roles which can set specific permissions for players:
- Operator, which enables all permissions, including operator commands, world settings, teleportation, and all of member permissions.
- Member, which enables mining, building, world and entities interactions.
- Visitor, which only lets players view or observe the world only, with none of the permissions enabled.
- Custom, which enables specific permissions set by operators. Following permissions can be applied for custom role:
| Option | Description | Default |
|---|---|---|
| Build | Allows the player to place blocks and entities in the world. | File:Ore UI - Toggle ON Button (Bedrock).png |
| Mine | Allows the player to break blocks in the world. | File:Ore UI - Toggle ON Button (Bedrock).png |
| Use doors and switches | Allows the player to use Minecraft:doors, Minecraft:levers, and Minecraft:buttons. | File:Ore UI - Toggle ON Button (Bedrock).png |
| Open containers | Allows the player to open the GUI of containers (Minecraft:chests, Minecraft:hoppers, Minecraft:crafters, etc). | File:Ore UI - Toggle ON Button (Bedrock).png |
| Attack Players | Allows the player to deal damage to players. | File:Ore UI - Toggle ON Button (Bedrock).png |
| Attack Mobs | Allows the player to deal damage to Minecraft:mobs. | File:Ore UI - Toggle ON Button (Bedrock).png |
| Operator Commands | Allows the player to execute operator Minecraft:commands. Also sets the player's permission level depending on the environment, see below. | Member: File:Ore UI - Toggle OFF Button (Bedrock).png |
| Teleport | Allows the player to use the
Template:Redr command. |
Member: File:Ore UI - Toggle OFF Button (Bedrock).png |
The owner of the world can change any player permissions, regardless of its own permissions. Other players can't change any player permissions unless if they are operators, but they can still view them for themselves and other joined players.
Player permissions differ from Minecraft:permission level, the latter enables and restricts specific commands, requiring different level for each command. Additionally, the "Operator Commands" permission if enabled sets the player's permission level to 3 in singleplayer or Minecraft:LAN world. In Minecraft:Bedrock Dedicated Server, it sets the permission level to 1.<section end="player-permissions"/>
Situations
Java Edition
- For a function:
- When parsing a function (including macro line parsing), the permission level defaults to 2 (but it can be changed in Minecraft:server.properties).
- When calling a function, see Minecraft:command context for details.
- For a player:
- If the player is an operator in a dedicated server, their permission level can be specified in the ops.json file. and its default value is specified in Minecraft:server.properties.
- If the player is the owner or another operator in a Realm, their permission level is 2.
- Unless the Realm is playing a minigame: then the owner's permission level is 0, and no one else can be operators.<ref>https://atlas.minecraft.net/guidelines</ref>
- If the player is in a singleplayer world, and cheats were enabled when creating the world, their permission level is 4.
- If the player is the owner of a LAN world, and cheats were enabled when creating the world, their permission level is 4.
- All players in a command-allowed LAN world have a permission level of 4.
- Otherwise, the player's permission level is 0.
- For other command executors, see Minecraft:command context for details.
- For raw JSON text resolution executors, see Minecraft:command context for details.
Bedrock Edition
- For a function:
- When parsing a function, the permission level is 1.
- When calling a function, see Minecraft:command context for details.
- For a player:
- In a dedicated server, if the player's "Operator Commands" option is enabled in the "Player Permission" screen, their permission level is 1.
- In a singleplayer world or a LAN world, if the player's "Operator Commands" option is enabled in the "Player Permission" screen, permission level is 3.
- Otherwise, the player's permission level is 0.
- For other command executors, see Minecraft:command context for details.
History
Template:Message boxTemplate:Article other Template:Missing information
Java Edition
Bedrock Edition
Issues
Script error: No such module "Issue list".
Gallery
Bedrock Edition
-
The "Player Permissions" screen.
-
The "Player Permissions" screen from other players.
-
The "Player Permissions" screen when all options are locked, in a server.
Minecraft Education
-
The "Player Permissions" screen.
See also
- Minecraft:Commands are mainly what dictated by permission level.
- Minecraft:Server.properties has a related property for setting operators' permission level.
- Minecraft:Commands/op sets player's operator status, granting or revoking them of operator permissions.
- Minecraft:Commands/permission sets player's specific permission level.
- Minecraft:Ore UI, the Bedrock Edition UI refresh.
References
<references />
ja:権限レベル pt:Nível de permissão ru:Уровень доступа uk:Рівень дозволу zh:权限等级