Upstream/Multiverse-Core
1
0
Fork 0
mirror of https://github.com/Multiverse/Multiverse-Core.git synced 2024-11-24 19:46:09 +01:00
Code Issues Projects Releases Wiki Activity

Updated Permissions (markdown)

Jad 2019-08-20 21:06:19 -05:00
parent 369eea6e4a
commit 0ef4d53445
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Permissions.md

@ -15,7 +15,7 @@ Multiverse allows you to control who can enter worlds via permissions! When you
If you give a user `multiverse.access.*` they can go to all worlds. If you give a user `multiverse.access.*` they can go to all worlds.
<!-- Outdated plugin: <!-- Outdated plugin:
## About PermissionsBukkit ## About PermissionsBukkit
[PermissionsBukkit](http://forums.bukkit.org/threads/26785) is the Official Bukkit plugin to manage permissions using the new [Permissions API](http://forums.bukkit.org/threads/25080/). Other permission plugins will probably begin incorporating the API to manage your servers permissions, but for now, the official plugin([PermissionsBukkit](http://forums.bukkit.org/threads/26785)) is what we have. Luckily, there is a bridge included with [PermissionsBukkit](http://forums.bukkit.org/threads/26785) to satisfy plugins still requesting Permissions 2.7/3.1 and will bridge those requests through and handle them. The bridge is **not** required to use permissions with Multiverse 2. [PermissionsBukkit](http://forums.bukkit.org/threads/26785) is the Official Bukkit plugin to manage permissions using the new [Permissions API](http://forums.bukkit.org/threads/25080/). Other permission plugins will probably begin incorporating the API to manage your server's permissions, but for now, the official plugin([PermissionsBukkit](http://forums.bukkit.org/threads/26785)) is what we have. Luckily, there is a bridge included with [PermissionsBukkit](http://forums.bukkit.org/threads/26785) to satisfy plugins still requesting Permissions 2.7/3.1 and will bridge those requests through and handle them. The bridge is **not** required to use permissions with Multiverse 2.
## PermissionsBukkit `config.yml` ## PermissionsBukkit `config.yml`
### NOTE: This is the config.yml that resides within the PermissionsBukkit folder! ### NOTE: This is the config.yml that resides within the PermissionsBukkit folder!
@ -42,13 +42,13 @@ Setting up the permissions in the config is pretty straight forward. You may fin
build: '&cYou do not have permission to build here.' build: '&cYou do not have permission to build here.'
``` ```
With this setup, all users will have the ability to teleport themselves using the [`/mvtp`](https://github.com/Multiverse/Multiverse-Core/wiki/Command-Reference#teleport) command, while users assigned to the admin group will also have the ability create worlds. Notice also that the admin has `permissions.*: true` and therefore can use the PermissionsBukkit commands in game. This may be especially useful for Multiverse 2. With this setup, all users will have the ability to teleport themselves using the [`/mvtp`](https://github.com/Multiverse/Multiverse-Core/wiki/Command-Reference#teleport-command) command, while users assigned to the admin group will also have the ability create worlds. Notice also that the admin has `permissions.*: true` and therefore can use the PermissionsBukkit commands in-game. This may be especially useful for Multiverse 2.
--> -->
### MV2 Permissions ### MV2 Permissions
You can use: `multiverse.*` to give someone all permissions for Multiverse. If you only want to give someone access to all worlds, use: `multiverse.access.*` for example. You can use: `multiverse.*` to give someone all permissions for Multiverse. If you only want to give someone access to all worlds, use: `multiverse.access.*` for example.
## Setting Permissions in game ## Setting Permissions in-game
Multiverse has the courtesy to show which permission node is needed for a command if you enter a /command and it fails due to permissions. Having this info readily available to you in the game can save you some time looking up the permission, and allow you to enter that permission into a group on the spot if need be. An admin can simply enter permissions in as you need them. For example, you try to run [`/mvlist`](https://github.com/Multiverse/Multiverse-Core/wiki/Command-Reference#list) and oh my you don't have permission, but you will be notified that you need `multiverse.world.list` permission node. Entering Multiverse has the courtesy to show which permission node is needed for a command if you enter a /command and it fails due to permissions. Having this info readily available to you in the game can save you some time looking up the permission, and allow you to enter that permission into a group on the spot if need be. An admin can simply enter permissions in as you need them. For example, you try to run [`/mvlist`](https://github.com/Multiverse/Multiverse-Core/wiki/Command-Reference#list-command) and oh my you don't have permission, but you will be notified that you need `multiverse.world.list` permission node. Entering
([LuckPerms](https://www.spigotmc.org/resources/luckperms-an-advanced-permissions-plugin.28140/) is required for this command, otherwise, use your permission plugin's command!) ([LuckPerms](https://www.spigotmc.org/resources/luckperms-an-advanced-permissions-plugin.28140/) is required for this command, otherwise, use your permission plugin's command!)