Skip to content

Admin Settings

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

Admin Settings

Rename a vanilla stick exactly AdminGriefControl, then use it or interact while holding it. The menu checks actual operator status; the item name cannot grant access.

AdminGriefControl

The main menu contains nine sections.

1. World Settings

  • Add-on enabled — master switch for all protection. Default: On.
  • Explosion scope — Global, Ward, or Hybrid. Default: Hybrid.
  • Protection Runes enabled — master switch for rune-local behavior. Default: On.
  • Player protection enabled — master switch for player-action restrictions. Default: On.
  • Admin-only rune placement — only operators may place runes. Default: Off.
  • Rune upgrades enabled — permits upgrades. Default: On.
  • Allow different-owner overlap — permits overlap when Minimum rune distance is zero. Default: Off.
  • Minimum rune distance — required separation from 0 through 128. Default: 0.
  • Operator bypass — lets operators ignore rune player restrictions. Default: On.
  • Grid enabled — master switch for persistent and preview grids. Default: On.
  • Console logging — prints protected-explosion summaries. Default: Off.

Same-owner runes may overlap or stack. Different-owner overlap requires Allow overlap on and Minimum distance zero. A positive minimum distance enforces a horizontal gap when rune centers are within 40 vertical blocks.

2. Protection Feature Switches

Each is a world master switch and defaults on:

  • Block placement
  • Block breaking
  • Containers
  • Block interaction
  • Item use
  • Entity interaction
  • Attack entities
  • PvP

Turning one off suspends that category of player restriction across every rune. It does not erase rune settings.

3. Explosion Source Switches

Each source defaults on:

  • Creeper
  • Charged Creeper
  • Ghast
  • TNT
  • TNT Minecart
  • End Crystal
  • Wither
  • Wither Skull
  • Unknown

This layer is authoritative. A disabled world source cannot be protected by a dimension or rune.

4. Dimension Explosion Rules

The Overworld, Nether, and End each have independent:

  • Enabled switch
  • All, Critical, Storage, Redstone, or Custom block mode
  • Nine source switches plus Custom
  • Nine entity-damage switches plus Custom
  • Apply-preset action

Each dimension starts enabled. The default preset is Survival Balanced, which protects Creeper, Charged Creeper, and Ghast blocks in All mode. Entity-damage protection starts off.

Applying a preset replaces the dimension's mode and source switches and resets its damage switches to off.

5. Default Presets and Limits

  • Maximum rune tier: Tier I through V. Default: V.
  • Maximum radius: 1–256. Default: 256.
  • Maximum runes per player: 1–64. Default: 8.
  • Maximum trusted members per rune: 0–48. Default: 24.
  • Upgrade cost: Standard, Expensive, or Free. Default: Standard.
  • Default player profile: Open, Build, Storage, Base, or Private. Default: Base.
  • Default explosion preset: Vanilla, Creeper Safe, Mob Explosion Safe, Survival Balanced, Build Safe, or Full Protection. Default: Survival Balanced.

The world also has a hard storage cap of 512 registered runes.

Reducing a maximum constrains later choices. Review existing high-tier or large-radius runes when tightening server policy.

6. Manage All Runes

Browse world records and filter them by the available owner or location information. An operator can:

  • Inspect identity, owner, dimension, position, tier, radius, and state
  • Open settings
  • Enable or disable the record
  • Transfer it to an online player
  • Remove a stale record

Remove deletes the registration only. Use it for a rune block already removed by a command, editor, or damaged world state.

7. Custom Protected Blocks

Enter up to 128 comma-separated block identifiers such as namespace:block_name.

The custom list:

  • Is included in Critical mode
  • Is included in Storage mode
  • Is included in Redstone mode
  • Is the complete protected set in Custom mode

Use exact identifiers. Invalid or misspelled identifiers will not match blocks.

8. Custom Explosion Sources

Enter up to 128 comma-separated entity identifiers such as namespace:entity_name. Matching explosive entities are classified as Custom and follow active Custom dimension and rune switches. Custom entity-damage protection has its own switch.

9. Status and Limitations

Displays active master settings and a concise description of the protection boundary. Use it to confirm whether the add-on, runes, player rules, grids, and explosion scope are enabled.

Changes and logging

Settings apply immediately and persist with the world. Administrative mutations are logged. Protected-explosion summaries obey the Console logging switch.

For headless administration, see Dedicated Server Console.

Clone this wiki locally