Skip to content

Rights and Roles

Version: 2.0.0 (not released yet)

Inside a claim, the role of a player decides what they may do, not a permission node. Each claim has its own rights table, and each zone of a claim can set single rights differently. Server zones have fixed rules of their own. Permission nodes only decide who may use the commands and windows, see Permissions.


RoleWhoNotes
VisitorEveryone without a role in the claimCan never get the right “Manage people and settings”
TrustedPlayers the owner or a manager addedThe role you get with Add or /ksclaim trust <player>
Co-ownerPlayers the owner made co-ownerOnly the owner gives and takes this role
OwnerThe player who owns the claimAlways has every right. Has no column in the table

Higher roles keep what the lower ones may. Whatever visitors may, trusted players and co-owners may too, and whatever trusted players may, co-owners may too. In the rights table such inherited ticks are shown dimmed and cannot be clicked. Taking a right from visitors does not take it from trusted players who have it ticked themselves.

  • Release chunks and dissolve the claim.
  • Hand the claim over (/ksclaim transfer).
  • Give or take the role Co-owner, take the role from a co-owner, and ban a co-owner.
  • Change the Co-owner column and the Manage people and settings row of the rights table.

What “Manage people and settings” allows

Section titled “What “Manage people and settings” allows”

Players with this right (co-owners by default) may:

  • add trusted players, take their role away, ban and unban players,
  • change the Visitor and Trusted columns of the rights table,
  • create, rename and delete zones and change their rules,
  • change the name, the greeting and the claim settings, and set or remove the home.

They can never release chunks, dissolve the claim or hand it over. Nobody can change their own role or the owner.

Leaving a claim: a trusted player or co-owner gives up their own role with Leave on the Claims or Settings tab. The owner cannot leave a claim; they hand it over instead.


The names are the ones in the window. Every right is checked where the action happens: at the block, at the creature, where the player stands when they drop or pick up an item, or at the home.

RightWhat it coversVisitorTrustedCo-owner
Build and breakPlacing and breaking blocks, harvesting crops, carrying a block away, buckets and placing fluids, hoe and fertiliser, hammer, sickle. A placed block needs the right in every chunk it reaches into–yesyes
Open containersChests, barrels and every other block with storage–yesyes
Doors and gatesDoors, gates and trapdoors. A double door that reaches into another chunk needs the right there too–yesyes
Use benchesWorkbenches and furnaces–yesyes
Switches, levers and portalsEvery other use of a block that is not one of the rows above–yesyes
Sit on seatsChairs, stools and other seatsyesyesyes
Feed and ride animalsUsing a creature with the use key: feeding, riding, talking to it. This also decides whether someone can talk to an NPC that stands in the claim–yesyes
Hurt animalsHurting animals, pets, NPCs and other creatures that are not hostile. Monsters can always be fought––yes
Pick up itemsPicking up an item on purpose. Walking over items cannot be stoppedyesyesyes
Drop itemsDropping itemsyesyesyes
Use the homeTravelling to the claim home–yesyes
Manage people and settingsSee abovenever–yes

Lighting a fire follows the claim setting Fire only with the build right: while it is on (the default) and the admin switch Only people with rights light fires is on too, lighting a fire needs Build and break. Otherwise everyone who is not banned may light a fire there.

Exceptions. Blocks whose ID contains a word from the admin’s exception list can be used by everyone (by default gravestone and mailbox), or broken by everyone (empty by default). See Configuration.

Creatures change nothing in claims and server zones: they do not break, place or use blocks there (admin switch Creatures break nothing).

On the Rights tab, click a checkbox to switch a right. Dimmed ticks come from a lower role and cannot be clicked. The Visitor × Manage people and settings cell is always empty.


A zone is a part of a claim with its own rules for visitors and trusted players.

  • A zone holds chunks of its claim only, and a chunk belongs to at most one zone. A claim has up to 10 zones (general.maxZonesPerClaim).
  • Zones are made on the Map tab in the mode Pick zone and get a name of 3 to 24 characters and their own colour.
  • Releasing chunks takes them out of their zone. A zone without chunks is removed.
  • The Zones tab lists the zones, shows a mini map and the rules of the chosen zone. Rename and Delete are there too. Deleting a zone removes its rules; its chunks stay part of the claim.

For Visitors and Trusted there is one cell per right (all rights except “Manage people and settings”). A click switches to the next of three states:

StateMeaning
like the claimThe rights table of the claim decides (the default)
allowedThe role may do this inside the zone
forbiddenThe role may not do this inside the zone
  • There are no zone rules for co-owners and the owner.
  • What visitors may do in the zone, trusted players may do too, even where the Trusted cell says forbidden. Such a cell shows inherited and cannot be clicked.

Examples:

  • A shop: set Visitors · Doors and gates to allowed. Visitors can open the shop doors, but no other doors in the claim.
  • A garden: set Trusted · Build and break to forbidden. Trusted players can still care for the animals there, but cannot break anything.

On the Settings tab, under What may happen here and Display. Players with “Manage people and settings” switch them.

SettingDefaultWhat it does
Fights between playersoffOff: nobody can hurt other players here
Explosions damage blocksoffOff: bombs and blast barrels leave everything standing
Fire only with the build rightonOn: only people who may build here can light fire
Flying for trusted peopleoffOnly when the server allows flying in claims
Keep inventory on deathoffOnly when the server allows it
Border when enteringonA short glowing line along the edge when someone enters
Greeting at the toponName and greeting when someone enters
  • Fights between players work from both sides: while they are off, nobody can hurt a player who stands in the claim, and nobody standing in the claim can hurt a player outside. Admins follow the same rule.
  • Explosions damage blocks only counts while the admin switch Stop explosions is on. While that switch is off, explosions break blocks in every claim.
  • Explosions without a known thrower do not hurt players where fights are off, and do not hurt peaceful creatures where explosions are off.
  • Flying. When the admin allows flying in claims, the owner and co-owners may fly in their claim. Trusted players may fly too while Flying for trusted people is on. Leaving the claim ends the flight, and for 10 seconds falls do no damage.
  • Keep inventory on death. When the admin allows it and the switch is on, everyone who dies in the claim keeps their items.
  • Switches the admin has not allowed are grey with Not released by the server. A switch that is already on can still be switched off.

  • A ban takes the role away. A banned player must be unbanned before they can get a role again.
  • Banned players cannot enter the claim. Who walks in is pushed back to where they last stood before, or to the nearest chunk they may stand on, with the notice No entry and one chat line. The claim log records it.
  • Banned players cannot travel to the claim home and get no rights there, not even through guild land.
  • Lift a ban with Lift on the Rights tab or /ksclaim unban <player>.

Server zones are made by admins (/ksclaimadmin zone create or the admin window). They belong to nobody, nobody can claim chunks there, and there are no roles. Their rules apply to everyone. Admins with the protection bypass ignore them, except the rule for fights between players.

RuleDefaultMeaning
EnteronOff: nobody gets in except admins with the bypass. Players are pushed back
Build and breakoffPlacing and breaking blocks
Open containersoffFor example market chests
Doors and gatesonDoors, gates and trapdoors
Use benchesonWorkbenches and furnaces
Fights between playersoffPlayers may hurt each other
Explosions damage blocksoffExplosions break blocks
  • Everything else (switches, seats, animals, hurting animals, picking up and dropping items) is not limited in server zones.
  • Creatures change nothing there while the admin switch Creatures break nothing is on. The block exceptions work there too.
  • Each server zone has a name and an optional greeting, shown when someone enters.

With KyuubiSoft Guilds installed, a claim can become land of a guild:

  • A guild member who has the guild right to manage guild land stands in a claim they own and types /ksguild land add. The claim stays theirs.
  • Members of the guild from a chosen rank may use blocks there: containers, doors, benches, switches, seats, animals, items and the home. From a second chosen rank they may also build.
  • Claims never gives guild members more than what Trusted may do at that place, and zone rules for trusted players apply. Guild land never gives “Manage people and settings”. Banned players get nothing.
  • Players with their own role in the claim keep it. The guild only adds rights their role lacks.
  • Guild members see it as Guild land on the map and in the claim list. The notice on entering carries the guild’s label for everyone.
  • The distance to foreign land does not count guild land you may use.
  • The land stops being guild land when the claim is dissolved or handed over, or when its owner leaves the guild.

The guild side (ranks, /ksguild land) is described in the Guilds wiki.


When a player does something at a block, Claims asks in this order:

  1. Free land: allowed.
  2. Server zone: its rule decides. Rights without a rule are allowed, and the exception list applies.
  3. Claim: banned players are refused, the owner is allowed. Then the player’s role and every lower role: a zone rule allowed or forbidden for that role, else the rights table. The first that allows decides.
  4. Guild land: extra rights from the guild, at most those of Trusted at that place.
  5. Exceptions: blocks on the admin’s exception list.
  6. Bypass: a refusal becomes “allowed” for admins with ks.claims.admin.bypass or the session bypass.

A refusal shows a notice and is written to the claim log, see UI Pages.