Skip to content

Player Protection and Trust

Charles Gantt edited this page Sep 11, 2026 · 1 revision

Player Protection and Trust

Rune restrictions apply to visitors. The owner, operators with bypass enabled, and trusted members with the needed permission may perform the action.

Protection profiles

Player protection profiles, first section

Player protection profiles, second section

  • Open: no tracked action is restricted.
  • Build: restricts Block placement and Block breaking.
  • Storage: restricts Block placement, Block breaking, and Containers.
  • Base: restricts Block placement, Block breaking, Containers, Item use, Entity interaction, and Attack entities. Ordinary Block interaction and PvP remain open.
  • Private: restricts every tracked action except PvP. Enable the PvP restriction separately when needed.

Applying a profile replaces the current list. Use Player Restrictions afterward to make precise changes.

Individual restrictions

Player restrictions, first section

Player restrictions, second section

  • Block placement: recognized placements at the selected or adjacent position.
  • Block breaking: attempts to break blocks within the volume.
  • Containers: recognized storage or inventory block access.
  • Block interaction: ordinary block interactions not handled as containers.
  • Item use: supported held-item use at a protected position.
  • Entity interaction: interacting with an entity.
  • Attack entities: direct player-attributed damage to a non-player entity.
  • PvP: direct player-attributed damage to another player.

The world Protection Feature Switches are master controls. When a feature is disabled worldwide, that category of rune restriction is suspended.

Trusted member roles

Trusted members

The owner or an operator can select an online player and assign:

  • Visitor: Block interaction.
  • Friend: Block interaction and Entity interaction.
  • Builder: Block placement, Block breaking, Containers, Block interaction, Item use, and Entity interaction.
  • Technician: Containers, Block interaction, Item use, and Entity interaction.
  • Manager: all eight action permissions and routine configuration access.
  • Custom: any exact combination of the eight permissions.

The role grants permission for actions the rune would otherwise deny. Manager additionally opens the rune menu, but it does not confer ownership. Managers cannot break or upgrade the rune, transfer it, or add, remove, or edit members.

Membership records use the selected player's persistent identity. The target must be online when first added or when ownership is transferred.

Ownership

The placer becomes owner. Owners can configure, break, upgrade, transfer, and manage members. Operators can perform owner-level administration.

When ownership is transferred:

  1. The target must be online.
  2. The target becomes owner.
  3. The target is removed from the trusted-member list.
  4. The former owner loses owner permissions unless added back as a member.

Breaking a rune removes its record and drops a fresh Tier I item.

PlayerGriefControl personal menu

Rename a vanilla stick exactly PlayerGriefControl in an anvil.

PlayerGriefControl

Use it or interact while holding it. The menu contains:

  • Explosion feedback — Off: no protected-explosion message.
  • Explosion feedback — Compact: reports the number of blocks protected.
  • Explosion feedback — Detailed: reports the recognized source and protected-block count.
  • Warnings: shows or hides action-denial messages and explosion feedback. Turning this off never weakens enforcement.
  • Personal grid preview: allows or refuses that player's 30-second preview requests. It does not hide persistent grids created by other players.
  • Manageable runes: owned runes, all runes for operators, and Manager-access runes.

Feedback appears only when the player is near the protected explosion.

Direct rune access

The named stick is optional. Crouch and interact with the physical rune to open its settings immediately when you have owner, operator, or Manager access.

Overlapping runes

If several runes contain the same position, every applicable rune must allow the action. A permissive rune therefore cannot cancel a stricter neighboring rune.