Roles & permissions
The Role System
SCS2 replaces V1's simple member/visitor toggle with a full role hierarchy. Each player in a claim has a role that determines what they can and cannot do.
Default roles (from lowest to highest)
| Role | Description |
|---|---|
| VISITOR | Any player who is not a member of the claim. By default, visitors have very limited permissions (cannot build, open containers, etc.). |
| MEMBER | A player who has been invited and accepted. Members can build, use containers, and interact with the claim based on their permission set. |
| MODERATOR | A trusted member who can manage other members — invite, remove, kick, ban, promote, and demote players within the claim. |
| OWNER | The claim creator. Has full control: all permissions, can manage flags, rename the claim, transfer ownership, sell it, and more. |
Custom roles
Claim owners can create custom roles with custom permission sets. Custom roles sit between VISITOR and OWNER in the hierarchy and can be assigned unique names. The maximum number of custom roles per claim is controlled by the scs.limit.roles.<amount> permission or admin settings.
Promoting and demoting
/claim promote <player> [claim]
/claim demote <player> [claim]Moves a member up or down the role hierarchy. A moderator can promote members to moderator and demote other moderators to member. Only the owner can promote someone to moderator.
Permissions (135)
Each role has an independent set of 136 permissions that control exactly what players with that role can do inside the claim. Permissions are configured per claim — you can have different permission setups for each of your claims.
Permissions are organized into 5 categories in the GUI:
- Building & Blocks
- Redstone & Mechanisms
- Containers & Workstations
- Entities & Decorations
- Items, Movement & Misc
You can add more permission pages by creating menu_permissions_N.yml files in the guis/ folder (e.g., menu_permissions_6.yml). NextPage/BackPage buttons are automatically hidden when there are no more pages.
Block Permissions
These permissions control what players can do with blocks inside the claim:
| Permission | Description |
|---|---|
PLACE_BLOCK | Place any block |
DESTROY_BLOCK | Break any block |
DESTROY_SPAWNERS | Break mob spawners specifically |
USE_BUCKET | Place or collect water/lava with buckets |
TRAMPLE_CROPS | Trample farmland by jumping on it |
IGNITE_BLOCK | Set the ground on fire with flint & steel or a fire charge — the griefing one (burning builds, animals, pets) |
IGNITE_PORTAL | Light a nether portal frame (the flames land against obsidian). Separate from IGNITE_BLOCK since 2.7.0, so you can let players link portals without letting them start fires |
Since 2.7.0: lighting a candle or a campfire with flint & steel is checked against INTERACT_CANDLE / INTERACT_CAMPFIRE instead of IGNITE_BLOCK. Upgrading claims keep their previous IGNITE_BLOCK value for IGNITE_PORTAL, so nothing a role could do before is revoked.
These are player permissions. Fire started by nature — lava, lightning, fire spread, a dispenser — is governed by the FIRE_IGNITE flag instead. Before 2.7.0 that flag also blocked players, which prevented even the claim owner from lighting their own portal with no message at all.
Container & Interaction Permissions
These permissions control interactions with containers, workstations, and redstone components. There are 30+ individual permissions for fine-grained control:
Containers
INTERACT_CHEST, INTERACT_TRAP_CHEST, INTERACT_ENDER_CHEST, INTERACT_BARREL, INTERACT_SHULKER_BOX, INTERACT_HOPPER, INTERACT_DROPPER, INTERACT_DISPENSER, INTERACT_SHELF
Workstations
INTERACT_FURNACE, INTERACT_BLAST_FURNACE, INTERACT_SMOKER, INTERACT_BREWING_STAND, INTERACT_ANVIL, INTERACT_ENCHANTING_TABLE, INTERACT_BEACON, INTERACT_SMITHING_TABLE, INTERACT_LOOM, INTERACT_CARTOGRAPHY_TABLE, INTERACT_STONECUTTER, INTERACT_GRINDSTONE, INTERACT_CRAFTING_TABLE, INTERACT_CRAFTER, INTERACT_COMPOSTER, INTERACT_CAULDRON
Redstone & Mechanisms
INTERACT_BUTTON, INTERACT_LEVER, INTERACT_PRESSURE_PLATE, INTERACT_TRIPWIRE, INTERACT_COMPARATOR, INTERACT_REPEATER, INTERACT_NOTE_BLOCK, INTERACT_TARGET_BLOCK
Doors & Gates
INTERACT_DOOR, INTERACT_TRAPDOOR, INTERACT_FENCE_GATE
Spawners & Special Blocks
INTERACT_SPAWNER, INTERACT_TRIAL_SPAWNER, INTERACT_SCULK_CATALYST, INTERACT_SCULK_SHRIEKER, INTERACT_COMMAND_BLOCK, INTERACT_STRUCTURE_BLOCK, INTERACT_JIGSAW
Other Interactions
INTERACT_BELL, INTERACT_CAMPFIRE, INTERACT_CANDLE, INTERACT_FLOWER_POT, INTERACT_JUKEBOX, INTERACT_LECTERN_READ, INTERACT_LECTERN_TAKE, INTERACT_BOOKSHELF, INTERACT_DECORATED_POT, INTERACT_BRUSH_BLOCK, INTERACT_GLOW_BERRIES, INTERACT_SIGN, INTERACT_BED, INTERACT_DRAGON_EGG, INTERACT_VAULT
Lecterns split: INTERACT_LECTERN_READ only allows opening and reading the book already on the lectern (no item movement); INTERACT_LECTERN_TAKE covers placing a book on an empty lectern and removing the book that's there. Set READ on / TAKE off to expose a public reading lectern that no visitor can empty.
This level of granularity means you can, for example, allow visitors to use buttons and doors but not open chests — something impossible with V1's simple toggle system.
Entity Permissions
Fine-grained control over how players interact with entities inside the claim. Over 20 permissions cover every type of entity interaction:
| Permission | Description |
|---|---|
PLACE_ENTITY | Spawn entities (spawn eggs, etc.) |
INTERACT_ENTITY | Right-click entities (general) |
DAMAGE_HOSTILE | Deal damage to hostile mobs (zombies, skeletons, creepers…) and neutral mobs that can fight back (wolves, iron golems, bees, llamas…). Split from the old DAMAGE_ENTITY in 2.5.9 — existing claims keep their previous value on both halves. |
DAMAGE_PASSIVE | Deal damage to passive mobs (cows, pigs, sheep, villagers…) |
SHEAR_ENTITY | Shear sheep and mooshrooms |
FEED_ENTITY | Feed animals |
RIDE_ENTITY | Board vehicles (boats, minecarts) and mount untamed/wild horses (the right-click that starts taming). Checked on PlayerInteractEntityEvent. |
MOUNT_ENTITY | Sit on living mounts: tamed horses, donkeys, mules, camels, pigs, striders, llamas, etc. Boats & minecarts are covered by RIDE_ENTITY, not this. Checked on EntityMountEvent. |
INTERACT_MOUNT_INVENTORY | Open the inventory of a tamed mount — saddle, horse armor, and the chest of a donkey, mule or llama. Covers the sneak-right-click on the mount and the screen opened while riding it. (Added in 2.7.1; existing claims inherit their INTERACT_ENTITY value. Before that version, interacting with an entity with an empty hand skipped every entity permission, so anyone could open a mount's inventory inside a claim.) |
LEAD_ENTITY | Attach leads to entities |
NAME_TAG_ENTITY | Use name tags on entities |
BREED_ENTITY | Breed two animals together. Feeding a single animal stays under FEED_ENTITY; breeding that happens without a player (villagers, a dispenser) answers to the NATURAL_BREEDING flag |
TAME_ENTITY | Tame an animal inside the claim — wolves, cats, parrots, horses, llamas |
MILK_ENTITY | Milk cows and mooshrooms |
CAPTURE_ENTITY | Capture entities (e.g., with leads or buckets) |
INTERACT_VILLAGER | Trade with villagers |
INTERACT_GOLEM | Interact with iron / snow golems (offer flowers, etc.) |
TRADE_WANDERING_TRADER | Trade with wandering traders |
Armor Stands, Item Frames & Paintings
| Permission | Description |
|---|---|
PLACE_ARMOR_STAND | Place armor stands |
DESTROY_ARMOR_STAND | Break armor stands |
INTERACT_ARMOR_STAND | Modify armor stand equipment |
PLACE_ITEM_FRAME | Place item frames / glow item frames |
DESTROY_ITEM_FRAME | Break item frames |
INTERACT_ITEM_FRAME | Rotate items in item frames |
PLACE_PAINTING | Place paintings |
DESTROY_PAINTING | Break paintings |
INTERACT_PAINTING | Right-click paintings (cycle painting variant on 1.21+) |
Vehicles
PLACE_VEHICLE, DESTROY_VEHICLE, INTERACT_VEHICLE — control placement, destruction, and use of boats and minecarts.
Item Usage Permissions
These 15+ permissions control which items players can use inside the claim:
| Permission | Description |
|---|---|
USE_BOW_CROSSBOW | Fire bows and crossbows |
USE_TRIDENT | Throw tridents |
USE_ENDER_PEARL | Throw ender pearls |
USE_CHORUS_FRUIT | Eat chorus fruit (causes teleportation) |
USE_FIREWORK | Launch fireworks |
USE_FISHING_ROD | Cast fishing rods |
USE_WIND_CHARGE | Use wind charges |
USE_SHIELD | Block with shields |
USE_ELYTRA | Glide with elytra |
USE_POTION | Use splash/lingering potions |
USE_SPYGLASS | Use the spyglass |
USE_BRUSH | Use archaeology brushes |
USE_BUNDLE | Use bundles |
USE_MAP | Use maps |
USE_FIRE_CHARGE | Use fire charges |
USE_SNOWBALL | Throw snowballs |
USE_EGG | Throw eggs |
Player Action Permissions
These permissions control general player actions and movement within the claim:
| Permission | Description |
|---|---|
PICKUP_ITEM | Pick up dropped items |
DROP_ITEM | Drop items from inventory |
ENTER | Enter the claim (if disabled, the player is pushed back) |
LEAVE | Leave the claim (if disabled, the player is pushed back inside — useful for jails, event arenas) |
NATURAL_TELEPORT | Teleport into the claim by natural means — ender pearl, chorus fruit, nether/end portals, end gateways |
OTHER_TELEPORT | Teleport into the claim via a third-party plugin or command — /tp, /warp, /home, and /tpa / /tpaccept. It is false for VISITOR by default, which is why a player who accepts a teleport request from outside their claim members does not arrive. SCS's own teleports (/claim tp, /claim visit, /claim back, warp menus) are exempt since 2.7.1 — they run the claim's ban / ENTER / warp checks themselves. |
COMMAND_TELEPORT | Teleport to this claim with /claim tp <owner>:<claim> or by clicking it in /claim list. Only members can hold it (MEMBER, MODERATOR, custom roles) — it never appears for VISITOR. (Added in 2.6.4) |
FLY | Use /claim fly in the claim |
SLEEP | Sleep in beds |
EAT | Eat food |
DRINK | Drink potions |
CROUCH | Sneak (used by some interaction systems) |
FROSTWALKER | Activate Frost Walker enchantment |
PROJECTILE_LAUNCH | Launch any projectile |
TOTEM_USE | Activate Totem of Undying |
EQUIP_ARMOR | Equip armor |
EQUIP_ITEM | Equip items to offhand |
EXP_DROP_PICKUP | Pick up experience orbs |
USE_PORTAL | Travel through nether / end / custom portals located inside the claim |
CREATE_PORTAL | Cause a portal to appear in the claim — lighting a frame, or arriving from the other dimension and having the paired portal generated here. Denied for visitors by default, which is what stops a stranger's nether travel from carving obsidian into your claim (2.7.0) |
SCULK_SENSOR_TRIGGER | Cause sculk sensors to emit a redstone pulse via player movement / interaction |
RECEIVE_BEACON_EFFECTS | Receive the active beacon's potion effects while inside the claim |
NATURAL_HEALTH_REGEN | Naturally regenerate health (vanilla full-hunger regen) while inside the claim. Potion regen, golden apples, and command-driven heals are unaffected. |
Teleports coming from other plugins
OTHER_TELEPORT is what decides whether /tpa, /home, /warp and friends may drop a player inside a claim. Since it is false for visitors by default, a server-wide policy decides how strict that is: (2.7.1)
claims:
teleport:
plugin-teleports: CONSENT # STRICT | CONSENT | TRUST
consent-requires-role: MEMBER # role the player at the destination must have| Mode | Meaning |
|---|---|
STRICT | Always enforce OTHER_TELEPORT. A /tpaccept from a non-member never arrives. |
CONSENT | Enforce it, except when a member of the claim is standing at the destination — which is exactly what accepting a teleport request means. Recommended. |
TRUST | Never enforce it. Bans and the ENTER permission still apply. |
The plugin's own teleports (/claim tp, /claim visit, /claim back, the warp menus) are never affected by this setting: they run the claim's ban / ENTER / warp checks themselves before teleporting.
Each of these permissions is set independently per role. The default values for each role are defined in the configuration and can be changed globally with /scs resetPermissionsFlagsForAllPlayerClaims. To reset only one role at a time (e.g. just Visitor) across every claim, use /scs resetrole <role>.