Minecraft:Permission level: Difference between revisions
More actions
imported>Susko3 →Java Edition: List the stuff that Level 0 operators get compared to non-operators |
Remove broken links to missing pages |
||
| Line 10: | Line 10: | ||
'''Level 0 – Operator''' | '''Level 0 – Operator''' | ||
* The player can enable the | * The player can enable the TPS graph in the debug screen. | ||
* The player can see | * 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 <code>[[Minecraft:Server.properties#broadcast-console-to-ops|broadcast-console-to-ops]]</code> is enabled. | * The player can see command output from other operators and the server console if <code>[[Minecraft:Server.properties#broadcast-console-to-ops|broadcast-console-to-ops]]</code> is enabled. | ||
'''Level 1 – Moderator''' | '''Level 1 – Moderator''' | ||
* The player can bypass | * The player can bypass spawn protection. | ||
'''Level 2 – Gamemaster''' | '''Level 2 – Gamemaster''' | ||
* More | * More commands are available. | ||
* The player can use | * 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 {{key|F3+I}} | * The player can copy the server-side NBT data of an entity or a block entity when pressing the {{key|F3+I}} debug hotkey, and copy the client-side NBT data when pressing {{key|shift+F3+I}}. | ||
* The player can use {{key|F3+F4}} ( | * The player can use {{key|F3+F4}} (game mode switcher) and {{key|F3+N}} debug hotkey (toggle between Spectator and the previous game mode). | ||
* The player can change or lock | * 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" | * 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 {{cmd|tell}} and raw JSON texts. | ||
'''Level 3 – Admin''' | '''Level 3 – Admin''' | ||
| Line 33: | Line 33: | ||
=== ''Bedrock Edition'' === | === ''Bedrock Edition'' === | ||
{{IN|bedrock}}, permission levels mostly dictate which commands a | {{IN|bedrock}}, 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:{{note|The first names and commands are from [https://learn.microsoft.com/en-us/minecraft/creator/commands/commands the official documentation]. The second names are from the debug information of [[Minecraft:Bedrock Dedicated Server]].}} | The permission levels and their available commands are:{{note|The first names and commands are from [https://learn.microsoft.com/en-us/minecraft/creator/commands/commands the official documentation]. The second names are from the debug information of [[Minecraft:Bedrock Dedicated Server]].}} | ||
| Line 116: | Line 116: | ||
'''Level 2 – Admin / Host''' | '''Level 2 – Admin / Host''' | ||
Server | Server operator commands: | ||
* {{cmd|deop}} | * {{cmd|deop}} | ||
* {{cmd|op}} | * {{cmd|op}} | ||
| Line 145: | Line 145: | ||
{{Exclusive|Bedrock|section=1}} | {{Exclusive|Bedrock|section=1}} | ||
[[File:Ore UI - Game Menu - Player Permissions Screen Menu (Bedrock).png|380px|thumb|The Player Permissions menu {{in|be}}.]] | [[File:Ore UI - Game Menu - Player Permissions Screen Menu (Bedrock).png|380px|thumb|The Player Permissions menu {{in|be}}.]] | ||
<!-- Used for | <!-- Used for Tutorial:Menu_screen/Bedrock_Edition transclusion --> <section begin="player-permissions"/> | ||
Player permissions dictate what the player can and cannot do in a multiplayer game. For example, actions such as building, | 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: | There are four roles which can set specific permissions for players: | ||
| Line 173: | Line 173: | ||
|- | |- | ||
|Open containers | |Open containers | ||
|Allows the player to open the GUI of | |Allows the player to open the GUI of containers ([[Minecraft:chest]]s, [[Minecraft:hopper]]s, [[Minecraft:crafter]]s, etc). | ||
|[[File:Ore UI - Toggle ON Button (Bedrock).png|link=|55px]] | |[[File:Ore UI - Toggle ON Button (Bedrock).png|link=|55px]] | ||
|- | |- | ||
|Attack Players | |Attack Players | ||
|Allows the player to deal damage to | |Allows the player to deal damage to players. | ||
|[[File:Ore UI - Toggle ON Button (Bedrock).png|link=|55px]] | |[[File:Ore UI - Toggle ON Button (Bedrock).png|link=|55px]] | ||
|- | |- | ||
| Line 196: | Line 196: | ||
[[File:Ore UI - Toggle ON Button (Bedrock).png|link=|55px]] | [[File:Ore UI - Toggle ON Button (Bedrock).png|link=|55px]] | ||
|} | |} | ||
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 | 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"/> | 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"/> | ||
| Line 203: | Line 203: | ||
=== ''Java Edition'' === | === ''Java Edition'' === | ||
* For a function: | * For a function: | ||
** When | ** 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 | ** When calling a function, see [[Minecraft:command context]] for details. | ||
* For a player: | * For a player: | ||
** If the player is an operator in a dedicated server, their permission level can be specified in the | ** 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 [[Minecraft:Realms|Realm]], their permission level is 2. | ** If the player is the owner or another operator in a [[Minecraft:Realms|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> | *** 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 | ** 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 | ** 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 | ** All players in a command-allowed LAN world have a permission level of 4. | ||
** Otherwise, the player's permission level is 0. | ** Otherwise, the player's permission level is 0. | ||
* For other command executors, see [[Minecraft:command context]] for details. | * For other command executors, see [[Minecraft:command context]] for details. | ||
| Line 218: | Line 218: | ||
=== ''Bedrock Edition'' === | === ''Bedrock Edition'' === | ||
* For a function: | * For a function: | ||
** When | ** When parsing a function, the permission level is 1. | ||
** When calling a | ** When calling a function, see [[Minecraft:command context]] for details. | ||
* For a player: | * For a player: | ||
** In a | ** 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. | ** 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. | ** Otherwise, the player's permission level is 0. | ||
| Line 233: | Line 233: | ||
{{HistoryTable | {{HistoryTable | ||
|{{HistoryLine|java}} | |{{HistoryLine|java}} | ||
|{{HistoryLine||1.14.4|dev=Pre-Release 4|Added the <code>function-permission-level</code> option that controls what permission level | |{{HistoryLine||1.14.4|dev=Pre-Release 4|Added the <code>function-permission-level</code> option that controls what permission level functions have.}} | ||
}} | }} | ||
| Line 239: | Line 239: | ||
{{HistoryTable | {{HistoryTable | ||
|{{HistoryLine|bedrock}} | |{{HistoryLine|bedrock}} | ||
|{{HistoryLine||1.21.70|dev=Preview 1.21.70.22|[[File:New UI - Player Permissions Screen Menu (Bedrock Preview 1.21.70.22).png|53px]] Player Permissions screen in | |{{HistoryLine||1.21.70|dev=Preview 1.21.70.22|[[File:New UI - Player Permissions Screen Menu (Bedrock Preview 1.21.70.22).png|53px]] Player Permissions screen in Pause menu screen has been updated to match [[Minecraft:Ore UI]], available in [[Minecraft:Minecraft Preview|preview]] only.}} | ||
|{{HistoryLine|||dev=release|Player Permissions screen in | |{{HistoryLine|||dev=release|Player Permissions screen in Pause menu screen is released to the public and no longer in [[Minecraft:Minecraft Preview|preview]] only.}} | ||
}} | }} | ||
| Line 274: | Line 274: | ||
[[Category:Server]] | [[Category:Server]] | ||
ja:権限レベル | |||
pt:Nível de permissão | |||
ru:Уровень доступа | |||
uk:Рівень дозволу | |||
zh:权限等级 | |||
Revision as of 15:59, 9 April 2026
Permission level is used to describe the permissions a player or a command executor has.
For example, Template:In, Template:Cmd 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
Template:IN, 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 Template:Key debug hotkey, and copy the client-side NBT data when pressing Template:Key.
- The player can use Template:Key (game mode switcher) and Template:Key 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 Template:Cmd 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
Template:IN, 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:
Level 1 – Game Directors / Operator
Mostly commands that affect gameplay and entities: Template:Collapse
Level 2 – Admin / Host
Server operator commands:
Level 3 – Host / Automation
Server host commands:
Level 4 – Owner / Admin
Server administrator commands:
Player Permissions
<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:Cmd 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:Expand section Template:Incomplete section
Java Edition
Bedrock Edition
Issues
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 Template:BE UI refresh.
References
<references />
ja:権限レベル pt:Nível de permissão ru:Уровень доступа uk:Рівень дозволу zh:权限等级