Upstream/Multiverse-Core
1
0
Fork 0
mirror of https://github.com/Multiverse/Multiverse-Core.git synced 2024-11-27 21:23:30 +01:00
Code Issues Projects Releases Wiki Activity

Destroyed Permissions (markdown)

lortikarry 2011-12-16 02:28:22 -08:00
parent cc9425dde1
commit d0ea3a3634
1 changed files with 0 additions and 49 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
Permissions.md

@ -1,49 +0,0 @@
_NOTE: Are you looking for [[the List of all MV Permissions|Big List O Permissions]]?_
## <a name="perm" href="#wiki-perm">•</a>Multiverse World Permissions
Multiverse allows you to control who can enter worlds via permissions! When you create a world or import a world into Multiverse-Core, it automatically creates a permission: `multiverse.access.WORLDNAME`. If a player _has_ `multiverse.access.WORLDNAME`, then they can enter that world.
**NOTE:** Ensure you have opfallback **disabled** in your Multiverse `config.yml`. If `opfallback` is set to `true` (and it is by default currently) _anyone_ can go to _any_ world.
If you give a user `multiverse.access.*` they can go to all worlds.
## <a name="permbukkit" href="#wiki-permbukkit">•</a>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.
## <a name="config" href="#wiki-config">•</a>PermissionsBukkit config.yml
### NOTE: This is the config.yml that resides within the PermissionsBukkit folder!
Setting up the permissions in the config is pretty straight forward. You may find it similar to pre-1000 permission plugins. Here is an example config file which includes some permissions for Multiverse 2:
users:
myplayername:
permissions:
groups:
- admin
groups:
default:
permissions:
permissions.build: false
multiverse.core.tp.self: true
admin:
permissions:
permissions.*: true
multiverse.world.create: true
inheritance:
- default
messages:
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.
### 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.
## <a name="setup" href="#wiki-setup">•</a>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 dont have permission, but you will be notified that you need `multiverse.world.list` permission node. Entering
/perm group setperm admin multiverse.core.list true
will add the permission to your admin group and viola! you have permission to use that command. MV has a lot of commands and permissions, so adding them in a need-to-use basis can sometimes be easier.
## <a name="ops" href="#wiki-ops">•</a>Setting OP's
OP's by default have all the Multiverse permissions set to true. So the easiest way to give your admins all the Multiverse permissions is to just make them OP. Of course, this may not be the best option for everyone.