Skip to content

Permissions

grandwazir edited this page Aug 10, 2012 · 7 revisions

Each command has a permission assigned to it which is required for players to be able to use it. A list of all the permissions registered by the plugin, and their default settings, is available below.

dimensiondoor.access.* (default: op).
dimensiondoor.clear (default: op).
dimensiondoor.create (default: op).
dimensiondoor.info (default: op).
dimensiondoor.list (default: op).
dimensiondoor.load (default: op).
dimensiondoor.modify.* (default: op).
dimensiondoor.modify (default: op).
dimensiondoor.modify.difficulty (default: op).
dimensiondoor.modify.enabled (default: op).
dimensiondoor.modify.game_mode (default: op).
dimensiondoor.modify.spawn_monsters (default: op).
dimensiondoor.modify.spawn_animals (default: op).
dimensiondoor.modify.pvp (default: op).
dimensiondoor.modify.keep_spawn_in_memory (default: op).
dimensiondoor.modify.isolated_chat (default: op).
dimensiondoor.remove (default: op).
dimensiondoor.spawn (default: op).
dimensiondoor.teleport (default: op).
dimensiondoor.unload (default: op).

Per world access control

New to DimensionDoor 2.1.0 is the ability to control access to worlds through permissions. The permission that is required is dimensiondoor.access + world name. Players are always able to access the main world.

For example if I wanted to allow players to access the world 'restricted' I would have to give them the dimensiondoor.access.restricted permission node.

Give all permissions

You can also automatically give all current and future permissions to a player by assigning them the wildcard. Use this with caution as you may accidentally give people access to future features you did not otherwise intend them to have. It should really only be given to administrators.

dimensiondoor.*

Example configurations

One of the new features with the built in permissions system is that it is now possible to group permissions together into one node then assign that to groups and users. This is really very useful in keeping all your permissions organised.

I have included the groups that I use on my own server. You need to add these to your permissions.yml file and then assign them using a Permission manager that is aware of the built in system. There are some examples below that you can use.

Administration commands

dimensiondoor.administration:
  description: Assign all permissions for DimensionDoor.
  default: false
  children:
    dimensiondoor.create: true
    dimensiondoor.info: true
    dimensiondoor.list: true
    dimensiondoor.load: true
    dimensiondoor.modify.*: true
    dimensiondoor.remove: true
    dimensiondoor.spawn: true
    dimensiondoor.teleport: true
    dimensiondoor.template: true
    dimensiondoor.unload: true

Teleport and information only

dimensiondoor.users:
  description: Allows users to get world information and teleport to different worlds.
  default: false
  children:
    dimensiondoor.info: true
    dimensiondoor.teleport: true