Permissions

Permissions.md – Permission nodes

Below is a sensible starting matrix. Edit it to match any nodes you added or removed while customising the source-code.

Node	Default group	Grants
aach.help	Player	View plugin help (/aach)
aach.book	Player	Receive the achievements book
aach.stats	Player	Run /aach stats
aach.list	Player	Open the achievements GUI
aach.top	Player	View global leader-boards
aach.week	Player	View weekly leader-boards
aach.month	Player	View monthly leader-boards
aach.toggle	Player	Toggle notification messages
aach.admin.*	Staff	Wild-card: all administrative abilities
aach.admin.reload	Staff	Reload configuration
aach.admin.give	Staff	Grant achievements
aach.admin.take	Staff	Remove achievements
aach.admin.check	Staff	Check player achievements
aach.admin.inspect	Staff	Inspect who has an achievement
aach.admin.generate	Staff	Create vanilla advancements
aach.admin.migrate	Staff	DB migration / maintenance

Category-specific permissions (optional)

If you wish to lock certain achievement types behind gameplay ranks, enable UsePermissionsPerCategory: true in config.yml. You can then grant nodes like:

aach.category.BlockBreaking
aach.category.MobKills

Each node unlocks the corresponding category in /aach list and lets players progress in it.

Recommended permission setup examples

• Default players – aach.* minus admin nodes (most servers simply grant aach.*).
• Moderators – all player nodes plus aach.admin.check and aach.admin.inspect.
• Admins / owners – aach.admin.*.

⚠️ Always reload permissions before running /aach reload, otherwise the GUI may retain stale visibility rules.