Skip to content

Permissions

Version: 1.0.0

Guilds uses two layers:

  1. Permission nodes on the server decide who may use a command at all, who is an admin and who may open every lock.
  2. Rank rights inside each guild decide what a member may do in that guild: invite, kick, lock for the guild, use the storage, and so on. The leader sets them on the Ranks tab.

Command syntax is on the Commands page.


Every player command checks its own node ks.guilds.user.<action>. These nodes are allowed unless you set them to false. A player without one gets “You lack the permission for that.”

PermissionCommand
ks.guilds.user.open/ksguild (opens the guild window)
ks.guilds.user.create/ksguild create
ks.guilds.user.invite/ksguild invite
ks.guilds.user.accept/ksguild accept
ks.guilds.user.deny/ksguild deny
ks.guilds.user.join/ksguild join
ks.guilds.user.request/ksguild request
ks.guilds.user.withdraw/ksguild withdraw
ks.guilds.user.leave/ksguild leave
ks.guilds.user.kick/ksguild kick
ks.guilds.user.promote/ksguild promote
ks.guilds.user.demote/ksguild demote
ks.guilds.user.transfer/ksguild transfer
ks.guilds.user.disband/ksguild disband
ks.guilds.user.info/ksguild info
ks.guilds.user.contribute/ksguild contribute
ks.guilds.user.help/ksguild help
ks.guilds.user.lock/ksguild lock
ks.guilds.user.unlock/ksguild unlock
ks.guilds.user.lockinfo/ksguild lockinfo
ks.guilds.user.autolock/ksguild autolock
ks.guilds.user.home/ksguild home
ks.guilds.user.sethome/ksguild sethome, and the Set here button on the Settings tab (it runs this command)
ks.guilds.user.land/ksguild land add, remove and list (only with KyuubiSoft Claims 2.0)
ks.guilds.user.chat/gc and the guild chat mode. Without it, chat lines stay in the general chat even while the mode is on

PermissionWhat it unlocks
ks.guilds.admin/ksguild admin and the admin window, also from the Guilds tile in the /ksadmin hub. In the admin window: step into any guild as described on UI Pages. On locks, also with the normal commands: change and remove every lock, break every locked block, and lock blocks somebody else set down or that stand in someone else’s claim. Does not open locked blocks
ks.guilds.admin.bypassOpens and uses every locked chest, door and gate, breaks locked blocks, and may lock blocks somebody else set down or that stand in someone else’s claim
  • Give both to staff who should handle locks. ks.guilds.admin alone can remove a lock, but cannot open a locked chest while the lock is there.
  • Inside their own guild, admins follow the rank rights like everyone else when they use /ksguild or the guild window. Admin powers over guilds only apply in the admin window.
  • The /ksadmin hub needs Core’s ks.admin; the Guilds tile in it also checks ks.guilds.admin.
  • The lock window says “Admins always get in”; in game that means players with ks.guilds.admin.bypass.

These are not permission nodes. Each guild sets them per rank on the Ranks tab; only the leader may change them. The leader always has every right.

Right (as shown in the window)AllowsDefault ranks
Invite membersInvite playersOfficer, Veteran, Member
Accept join requestsAccept and decline join requestsOfficer, Veteran
Remove lower ranksRemove members of a lower rankOfficer
Promote and demote, up to below their own rankMove lower members one rank up or downOfficer
Write the announcementWrite and remove the announcementOfficer
Lock chests and doors for the guildCreate guild locksOfficer, Veteran, Member
Change and remove other members’ guild locksChange and remove any guild lock of the guild, and lock chests that a guild mate set downOfficer
Put items into the guild storagePut items inall ranks
Take items from the guild storageTake items out, up to the daily limit of the rankOfficer, Veteran, Member
Travel to the guild homeUse /ksguild home and To the guild homeall ranks
Set the guild homeSet and remove the guild homeLeader only
Manage guild landAdd and remove guild land and set its ranks (with Claims)Leader only

The admin sets the defaults for new guilds with defaultRights in config.json; existing guilds keep their own table.

Leader only, always: renaming the guild, changing tag, colour, crest and joining mode, the setting “No damage between members”, renaming ranks and changing rights, handing over the leadership and disbanding.

Fixed rules for locks:

WhoPrivate lockGuild lock
May openThe owner and the players added to itMembers from the lock’s rank, and the players added to it
May change or removeThe ownerWhoever set it (while in the guild) and members with Change and remove other members’ guild locks
May break the blockThe ownerWhoever set it (while in the guild) and ranks Officer and Leader

Players with ks.guilds.admin may change, remove and break every lock; players with ks.guilds.admin.bypass may open and break every lock. Creatures and explosions never break a locked block.


PermissionNote
ks.guilds.nameplate.tagGuild tags registered with KyuubiSoft Nameplates carry this node so players cannot pick another guild’s tag in the Nameplates tag list. Give it to nobody

/kslang has no permission.