Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9
UltimateClans permissions#
UltimateClans uses two different permission layers:
- Bukkit permissions decide whether a player can access a command/feature at server level.
- Clan roles/internal clan permissions decide whether that member is allowed to perform the action inside their clan.
Giving uclans.player.promote, for example, does not automatically let every member promote everyone. The clan hierarchy is still evaluated.
Recommended permission packages#
uclans.player#
This is the player permission package declared by the plugin. It grants the normal player command nodes such as clan creation, information, profiles, member management, settings, regroup, roles and module entry points included as children in the current plugin.yml.
Use it for a normal server rank when you want the standard UltimateClans experience, then remove individual child permissions if your permission plugin supports child negation and you want to restrict a feature.
uclans.admin.*#
Administrative wildcard/package for server staff. It includes destructive and force-management actions such as deleting clans, changing tags/leader, modifying points/slots, force joining/kicking and reloading.
Recommendation: grant this only to trusted staff. It is not a substitute for clan leadership permissions.
uclans.*#
Top-level wildcard declared by the plugin. It includes both player and administrative packages and is described as bypassing restrictions.
Recommendation: reserve it for owners/developers. Do not give it to normal moderators just to fix one missing permission.
Player command permissions#
| Permission | Used for | Typical assignment |
|---|---|---|
uclans.player.help | /clan help | Normal players |
uclans.player.create | Clan creation flow | Normal/VIP ranks depending on your server design |
uclans.player.cancel | Cancel interactive clan operations | Normal players |
uclans.player.changeleader | Leadership transfer command | Normal players; clan role checks still apply |
uclans.player.desc | Change clan description | Normal players; clan role checks still apply |
uclans.player.disband | Disband command | Usually normal players; only eligible leaders can complete it |
uclans.player.leave | Leave clan | Normal players |
uclans.player.join / uclans.player.deny | Join/invite response flow | Normal players |
uclans.player.promote / uclans.player.demote | Member rank changes | Normal players with clan authority |
uclans.player.home | Clan Home module/command branch | Give when Clan Home is enabled |
uclans.player.ff | Friendly-fire command | Give if players may control FF |
uclans.player.info / uclans.player.list | Clan information/listing | Normal players |
uclans.player.profile | Profile branch | Normal players |
uclans.player.member | Member management branch | Normal players; clan role checks apply |
uclans.player.settings | Clan settings | Normal players; clan role checks apply |
uclans.player.regroup | Regroup requests | Give when regroup is part of gameplay |
uclans.player.ban / uclans.player.unban | Clan ban list | Members with clan authority |
uclans.player.nickname | Nickname feature | Normal players if enabled |
uclans.player.role | Role view/set/sync flow | Normal players; role administration still validates authority |
uclans.player.language | Per-player language flow | Give if language switching is exposed |
Administrator permissions#
The current administrative command tree uses dedicated nodes such as uclans.admin.chatspy, addslot, setslot, removeslot, addpoints, setpoints, removepoints, changetag, resetplayerkdr, resetclankdr, globalff, delete, forcejoin, verify, reload, emptyclans, bank, kick, setleader, extension and module.
Grant the smallest node that matches the staff responsibility. For example, a moderator who only needs clan chat monitoring should receive uclans.admin.chatspy, not uclans.admin.*.
GUI permissions#
The current plugin.yml includes uclans.player.use_gui and uclans.admin.use_gui as child permissions. If commands work but a GUI refuses to open, check these nodes before debugging the GUI configuration.
Troubleshooting permissions#
- Test without OP: OP can hide missing permission nodes.
- Check both layers: a Bukkit permission may pass while a clan-role permission still blocks the action.
- Check module/addon permissions separately: addons can define their own namespaces rather than using
uclans.*. - Verify wildcard inheritance in your permission plugin; the nodes are declared in
plugin.yml, but inheritance/negation behavior is handled by the permission plugin.