AlphaRewardsDocs v2.0.0
AlphaRewardsReferencePermissions

Permissions

Four declared nodes, plus the tier permissions you define yourself in the menu files.

On this page

Declared in plugin.yml

NodeDefaultGrants
alpharewards.usetrueOpen the rewards GUI (/alpharewards with no args)
alpharewards.settingstrueOpen the settings GUI (/alpharewards settings)
alpharewards.autoclaimtrueActually receive auto-claim on join, and toggle the auto-claim setting in the Settings GUI (both gated by this one node)
alpharewards.adminop/setday, /alpharewards reload, /alpharewards reset
Three of these four default to 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 and streak.yml

  • alpharewards.tier.vip x2
  • alpharewards.tier.mvp x3
  • alpharewards.tier.elite x4

What x2, x3, x4 mean

In the shipped files the VIP tier gives twice the default reward, MVP three times and Elite four times. The multiplier is written into each tier's own command list, not computed by the plugin.

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.

The tier names shown above are just what ships in the example config — rename, add, or remove tiers freely to match your own server's rank ladder. Nothing about them is hardcoded in the plugin itself.

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.

List tiers lowest → highest in the file. If a higher tier is defined before a lower one, a player holding both permissions will incorrectly receive the lower tier's reward, since it's evaluated later and overwrites the match.