Permissions
EnhancedEchest uses Brigadier permission gates on every command. All nodes default to op, so out of the box only operators can use the commands. Grant the nodes below through your permission plugin (LuckPerms, etc.) to open them up to other ranks.
Player permission
/enderchest, /ec, /eclist) and use the Set as main action in the menu. Right-clicking an ender chest block never requires this. A player without it who owns several chests can never set a main, so block right-click always opens the management menu for them. enhancedechest.additional_amount.2.slot.54 grants two 54-slot chests. Multiple matching nodes stack (summed per size). Removing a node deletes exactly that many chests of that size again; any items they held spill into a temporary chest the player can recover from /eclist. See Permission-granted chests below. Permission-granted chests
Beyond the admin /ee add command, you can hand out ender chests purely through permissions with the enhancedechest.additional_amount.<count>.slot.<size> node. This is ideal for tying chest perks to ranks in LuckPerms (or any permission plugin).
<count>: how many chests to grant (a positive whole number).<size>: their slot count, a multiple of9from9to54. Invalid sizes are ignored.
The grants are synced every time the player opens their ender chest, so changes take effect on their next open, with no command or relog required.
How grants behave
- Stacking, not highest-wins. Every matching node is added up, grouped by size. Granting both
enhancedechest.additional_amount.1.slot.9andenhancedechest.additional_amount.2.slot.9gives the player three 9-slot chests. - Losing a node removes exactly those chests. Drop a rank and the matching chests are removed again; if they held items, those spill into a temporary chest recoverable from
/eclist, so nothing is destroyed. - The base chest is protected. Every player always keeps at least one regular chest. Permissions never create, delete, or override it.
- They behave like normal chests. Granted chests can be opened, renamed, given an icon, and set as the main chest; they carry no special tag or restriction. Only admin commands leave them alone:
/ee resizeand/ee deletewill not modify a permission-granted chest.
Disabling the feature
Permission grants are only applied while permission-chests.enabled is true in config.yml. Turning it off stops syncing but leaves any already-granted chests in place (they keep behaving as normal chests). See the Configuration page.
Admin permissions
Admin commands use a two-key model: every /ee subcommand checks the base node enhancedechest.command.admin and its own specific node below. Granting a specific node alone is not enough: the player also needs enhancedechest.command.admin. There is no inheritance between them.
/enhancedechest (/ee) admin command, in addition to the command-specific node. /ee add <player> <size> [duration] to give a player a new (optionally temporary) chest. /ee resize <player> <index> <size> to change a chest's slot count (spilling overflow on shrink). /ee delete <player> <count> [force] to delete the newest chests (spilling their items, or hard-deleting with force); the player's first chest is always kept. /ee view <player> [index] to open another player's chest. Read-only on its own: you can see the contents but not move items. enhancedechest.admin.view, lets you take and add items while viewing another player's chest. Without it, /ee view is look-only. /ee reload to reload the configuration and language files from disk. /ee migrate run <player> and /ee migrate run all to import vanilla ender chest contents. Granting admin access in one go
To give a moderator full admin access, grant both enhancedechest.command.admin and the specific nodes they need (or a wildcard like enhancedechest.admin.* if your permission plugin expands it, remembering they also need the plain enhancedechest.command.admin base node).