permissions.yml

#    SuperUser Permission nodes and example PEX 'permissions.yml'.
#    This file is in the SuperUser.jar file, ready to use.

#    These nodes directly correlate to field names in table va_superuser.
#    The presence of a node signifies 'true'.  The default value of 'false'
#    is used when the node is not present.

#    SuperUser uses these nodes when using the /rank command to initialize
#    the MySQL player record. They operate independently of PEX.  They may
#    be changed later and do not have anything to do with the PEX 
#    group.  The SU nodes here provide a means to set up the SU 
#    player record automatically for each PEX group.

#    In other words, the SU nodes do not define real-time protection
#    for the PEX group as appears here.  The SU player protection
#    comes from the settings on the MySQL player record.  The player
#    settings may be adjusted later, different for each player.

#    All nodes are true/false with 'true' meaning positive permission with
#    one exception.  The three gamemodes have a hierarchy with CREATIVE
#    being the highest and SURVIVAL the lowest.  ADVENTURE is in between.
#    Since permissions are built upon lower groups, higher ranking groups
#    will inherit more than one gammeode.  When interpreting the gamemode
#    setting, SU always tries the highest, creative, first and works its
#    way down to survival. The highest will be selected as the gamemode
#    definition.  As applies to a live player, a creative defined player
#    may change to lower game modes, but a survival defined player may not
#    change up, and triggers a breach if attempted.

#    THE SU NODES

#    - su.survival    sets player gamemode
#    - su.adventure        .
#    - su.creative         .
#    - su.is_op       sets player op status
#    - su.edit_ok     edit permission, ie: break or place blocks
#    - su.save_wrk    saves players work, otherwise rolled back at quit
#    - su.save_tnt    saves effects of TNT, otherwise rolled back at quit
#    - su.chat_ok     allow access the game chat
#    - su.bckt_ok     allow the use of buckets
#    - su.fly_ok      allows the player to fly
#    - su.tp_ok       allows the player to teleport
#    - su.tnt_ok      allows the use of TNT
#    - su.lava_ok     allows the use of lava
#    - su.mwrld_ok    allows inter world travel
#    - su.spwn_ok     allows the use of spawn eggs
#    - su.potn_ok     allows the use of potion
#    - su.we_ok       allows the use of commands starting with '//'
#    - su.hide_ok     allows hiding via vanish or potion
#    - su.k_plr_ok    allow attacking other players
#    - su.k_aml_ok    allow killing animals
#    - su.k_pet_ok    allow killing claimed pets

# NOTE: Extended permission nodes are generally not necessary for groups
# with op status.  In this configuration it starts with group: partner.
# Notice that the groups build on inherited permissions from the groups
# below them.

# SuperUser expects to find a group named 'guest'.  This is a group
# without privileges.  All other group names are left to your discretion.

groups:
  super:
    prefix: '&0(&cS&euper&0)&e '
    inheritance:
    - admin
    - partner
    - member
    - player
    permissions:
    - group.super
    - su.*
    options:
      rank: '1'
  admin:
    prefix: '&0(&5A&6dmin&0)&6 '
    inheritance:
    - partner
    - member
    - player
    permissions:
    - group.admin
    - su.save_tnt
    options:
      rank: '2'
  partner:
    prefix: '&0(&9P&bartner&0)&b '
    inheritance:
    - member
    - player
    permissions:
    - group.partner
    - su.is_op
    - su.creative
    - su.we_ok
    - su.hide_ok
    - su.k_pet_ok
    options:
      rank: '3'
  member:
    prefix: '&0(&aM&bember&0)&b '
    inheritance:
    - player
    permissions:
    - group.member
    - su.creative
    - su.fly_ok
    - su.tp_ok
    - su.tnt_ok
    - su.lava_ok
    - su.mwrld_ok
    - su.spwn_ok
    - su.potn_ok
    - bukkit.command.list
    - bukkit.command.teleport
    - essentials.clearinventory
    - essentials.warp
    - essentials.list
    - essentials.back
    - essentials.back.ondeath
    - essentials.sethome
    options:
      rank: '4'
  player:
    prefix: '&0(&2P&3layer&0)&3 '
    permissions:
    - group.player
    - su.survival
    - su.edit_ok
    - su.save_wrk
    - su.chat_ok
    - su.bckt_ok
    - su.k_plr_ok
    - su.k_aml_ok
    - bukkit.command.tell
    - bukkit.command.kill
    - bukkit.command.me
    - essentials.help
    - essentials.list
    - essentials.motd
    - essentials.rules
    - essentials.afk
    - essentials.balance
    - essentials.compass
    - essentials.depth
    - essentials.getpos
    - essentials.home
    - essentials.jump
    - essentials.mail
    - essentials.mail.send
    - essentials.mute
    - essentials.pay
    - essentials.rules
    - essentials.sethome
    options:
      rank: '5'
  guest:
    default: true
    prefix: '&0(&8G&7uest&0)&7 '
    permissions:
    - group.guest
    - su.survival
    options:
      rank: '6'

# There is no need to setup players as SuperUser manages them
# via the PEX api.  It is best to just leave this to SU.