Permissions
EssentialsLite uses Bukkit/Paper permission checks. Configure permissions through a generic permission manager; no specific permission plugin is required by this documentation.
Core Access
Grant only the nodes needed by each role. Common player nodes include:
essentials.sethometo create homesessentials.hometo use homesessentials.balanceto check a balanceessentials.payto send moneyessentials.settingsto open the settings menuessentials.nightvisionto toggle personal night vision
Most player utility and settings permissions default to true; administrative nodes generally default to op. Check the full permission reference before assigning wildcard nodes.
Home Limits
The default home limit is 1. Packaged permission tiers are:
| Home tier | Limit | Runtime permission |
|---|---|---|
| Configured base | 1 | home.default-limit (no default permission node) |
| VIP | 2 | essentials.home.limit.vip |
| MVP | 3 | essentials.home.limit.mvp |
| Elite | 4 | essentials.home.limit.elite |
| Legend | 5 | essentials.home.limit.legend |
| God | 6 | essentials.home.limit.god |
The effective limit uses the highest matching configured tier. Runtime home-limit nodes follow essentials.home.limit.<name>, where <name> is the configured home permission name.
Item Permissions
Some item-specific permissions are generated at runtime. Examples:
essentials.give.item-<material>for a specific materialessentials.spawner.<mob>for a specific mob spawner type
Use the exact lowercase runtime value exposed by the command or plugin behavior. These nodes are not a fixed, exhaustive list in this page.