The current (version 2.0 to 2.3) structure of the permissions is as follows:
betterenderchest betterenderchest.user (default: everyone) betterenderchest.user.craft betterenderchest.user.place betterenderchest.user.destroy betterenderchest.user.open betterenderchest.user.open.privatechest betterenderchest.user.open.publicchest betterenderchest.slots.upgrade1 (default: nobody) betterenderchest.slots.upgrade2 (default: nobody) (etcetera) betterenderchest.command (default: ops) betterenderchest.command.deleteinv betterenderchest.command.give betterenderchest.command.list betterenderchest.command.swapinv betterenderchest.command.reload betterenderchest.command.viewinv betterenderchest.command.viewinv.self betterenderchest.command.openinv betterenderchest.command.openinv.self
betterenderchest.user permissions give access to the basic Ender Chest actions. They are granted to everyone by default, but you can easily change this (see the documentation if your permission plugin).
betterenderchest.slots.upgradeX permissions give access to the specified rank. You can set in the configuration file how many upgrades there are and how many slots each upgrade has access to.
betterenderchest.command permissions give access to the various subcommands of
/bec). Each permission gives access to the subcommand with the same name.
viewinv is read-only, no items can be placed in or taken from the Ender Chest while
openinv also allows to place or take items. The
openinv commands also have a
.self child, which allows the user to view/open only his/her own Ender Chest.
/enderchest command doesn't have it's own permission. Instead, it looks to the
betterenderchest.command.openinv permissions. If, for example, the user has
betterenderchest.command.viewinv to remotely view all Ender Chest inventories and
betterenderchest.command.openinv.self to remotely open his/her own Ender Chest, he/she will be able to open his/her own Ender Chest with
/enderchest, and he/she can view any other Ender Chest with