Teddy563 Permissions Helper
Default permission engine: LuckPerms (luckperms.net/wiki). Vault bridges economy/perms
for plugins that read through it. Get the model right before writing nodes.
The four concepts (do not conflate them)
- Groups carry permissions; users inherit groups.
/lp creategroup vip,/lp group vip permission set essentials.fly true,/lp user Steve parent add vip. - Tracks are ordered ladders of groups for promotion/demotion only —
/lp track staff append helper,…append mod. Per the wiki: "tracks act only as a means for easy promotion and demotion… and do not influence inheritance."/lp user Steve promote staff. - Contexts (
key=value) restrict where a permission/parent/meta applies. Built-in keys:server,world,gamemode,dimension-type. Seereferences/luckperms-contexts.md. - Meta — prefix, suffix, weight, and custom meta keys (read elsewhere via PlaceholderAPI
%luckperms_meta_key%)./lp group vip meta setprefix 10 "&a[VIP] ".
Node convention
plugin.feature.action, e.g. essentials.home.multiple.vip, worldguard.region.bypass.
Wildcards (essentials.home.*) work but were historically discouraged in Bukkit; LuckPerms can
apply child permissions with apply-bukkit-child-permissions: true. Prefer explicit nodes for
auditability; use wildcards knowingly.
Inheritance & prefix resolution
- Primary-group calculation defaults to
parents-by-weight. Give groups a weight (/lp group admin meta setweight 100) so the highest-weight group wins prefix/suffix. - Negated nodes (
-some.node) override positives by specificity/weight — use to carve exceptions. - Temporary perms/parents:
/lp user Steve permission settemp … 7d.
Networks (multiple servers, one DB)
- Point every backend at the same LuckPerms SQL database for a shared identity.
- Use static server contexts (per-server
contexts.yml, e.g.server-type=skyblock) or the server'sservercontext so one DB grants per-server perks without leaking them network-wide. - Run LuckPerms on the Velocity proxy too (LuckPerms-Velocity) for proxy-level perms; keep the API jar versions aligned across proxy and backends, or contexts break on update.
Working method
- Establish the rank ladder (groups + a track) before assigning individual nodes.
- Scope with contexts when a perk is per-world/per-server/per-gamemode.
- Set weights for clean prefix resolution.
- When unsure of a plugin's exact node names, call
learn-plugin-docsfor that plugin and read its permissions section — do not invent nodes. - Give the user the exact
/lp …commands to run, in order.