Permissions
Four real permission nodes are declared in plugin.yml. Reward-tier nodes (VIP-style bonuses) are a second, fully admin-defined layer that lives in the menu YAML files instead — they aren't declared anywhere, so your permissions plugin needs to grant them explicitly.
Declared in plugin.yml
| Node | Default | Grants |
|---|---|---|
alpharewards.use | true | Open the rewards GUI (/alpharewards with no args) |
alpharewards.settings | true | Open the settings GUI (/alpharewards settings) |
alpharewards.autoclaim | true | Actually receive auto-claim on join, and toggle the auto-claim setting in the Settings GUI (both gated by this one node) |
alpharewards.admin | op | /setday, /alpharewards reload, /alpharewards reset |
true — granted to every player automatically, no permissions plugin required. Only alpharewards.admin defaults to op.Reward-tier permissions
Not declared in plugin.yml — these are arbitrary strings you assign yourself inside each reward day's commands block in menus/daily.yml / menus/streak.yml. The shipped example files use:
daily.yml
alpharewards.tier.vipalpharewards.tier.mvp
streak.yml
alpharewards.tier.vipalpharewards.tier.mvpalpharewards.tier.elitealpharewards.tier.legendalpharewards.tier.titanalpharewards.tier.derex
Grant these yourself
Through LuckPerms or your own permissions plugin — nothing in AlphaRewards grants these nodes automatically, and their key names/count are entirely up to you.
Tier order
Tiers are evaluated by walking the YAML section top to bottom, and every matching tier overwrites the previous match rather than stopping at the first (or best) one. That means whichever matching tier is listed last in the file wins — not necessarily the highest-value one semantically.