Skip to content

Administrator Guide

Jump to bottom
Jack edited this page May 12, 2026 · 2 revisions

Administrator's Guide

You probably don't need to read this entire document just to get started with GriefPrevention3D. The plugin does almost all the work for you — try it out and come back here when something isn't obvious.

Table of Contents

Administrative Claims

Required permission: griefprevention.adminclaims

Administrative claims are reserved areas owned by "the administration" rather than a specific player. They don't cost any player claim blocks, and any player with admin claims permission can modify all administrative claims.

  • Want to grant all players permissions in admin claims? /accesstrust public, /containertrust public, or /trust public works.
  • Want to prevent players from claiming an area without stopping them from building there? Drop an admin claim and /trust public inside it.

Use /adminclaims to switch to admin-claim mode and /basicclaims to switch back.

3D Administrative Claims

GP3D addition. Required permission: griefprevention.adminclaims

3D admin claims extend the admin claims system with exact vertical control. Instead of the standard ground-extension offset (which extends an admin claim from the clicked Y level down to the world floor), Admin3D mode uses the clicked Y coordinates directly as the vertical bounds of the claim.

  • /3dadminclaims (aliases: adminclaim3d, adminclaims3d, 3dadminclaim) — switch shovel to 3D admin claim mode.
  • /aclaim mode admin3d — same via the unified command handler.
  • /basicclaims — switch back to normal mode.

Behavior:

  • Clicked Y levels become the exact top and bottom of the claim — no automatic ground extension.
  • Free to create (no claim blocks consumed) with null owner ID (standard admin claims).
  • Minimum size and claim block checks are bypassed (identical to regular Admin mode).
  • Multiple 3D admin claims can stack at different Y levels inside the same X/Z footprint, useful for multi-floor admin structures.
  • Claim boundary visualization uses the ADMIN_CLAIM_3D visual style (glowstone/pumpkin by default) to distinguish 3D admin claims from other claim types.

Note: The existing /adminclaims (2D) mode continues to work as before. 3D admin claims are an additional tool, not a replacement.

Converting Claims Between Admin and Basic

GP3D addition. Required permission: griefprevention.adminclaims.convert

Two commands, no shovel dance:

  • /makeadmin — stand inside a basic (player-owned) claim and run the command. The claim becomes an administrative claim.
  • /makebasic — stand inside an administrative claim and run the command. It becomes a basic claim owned by you.

These preserve trust data, subdivisions, and claim geometry. They are safer than the classic /transferclaim workflow when you just need to flip the ownership category without handing the claim to another player. For the "hand an admin claim to player X" flow, use /transferclaim <player> instead.

Claim-block math notes:

  • /makeadmin does not refund blocks to the previous basic owner (they have lost the claim).
  • /makebasic does not deduct blocks from you beyond what the claim would normally cost. For this reason /makebasic is admin-only.

Changing Player Claims

Overriding

Required permission: griefprevention.ignoreclaims

Any player with this permission can bypass claim protections using /IgnoreClaims, allowing them to build, break, and change permissions (trust, untrust, etc.) anywhere. Admin claims still require griefprevention.adminclaims. Run /IgnoreClaims again to go back to "respecting claims" mode and avoid accidents.

Individual actions taken while ignoring claims are not logged, so only grant this to staff you trust 100%.

Deleting and Resizing

Required permission: griefprevention.deleteclaims

  • /deleteclaim — deletes the claim you're standing in, even if it's not yours. Deleting public (admin) claims additionally requires griefprevention.adminclaims.
  • /deleteallclaims <player> — deletes all of a specific player's claims, useful after permanent bans.

GP3D does not auto-remove claims for banned players because many servers have ban-appeal workflows. To do it automatically, alias your /ban command in commands.yml to also run /deleteallclaims <player>.

Anyone with griefprevention.deleteclaims may resize another player's claim with the golden shovel as if it were their own. The owner's claim block total is adjusted accordingly. There is no separate resize permission because resize can effectively un-claim any block (same risk surface as delete).

All deletions and resizes (except by the claim owner themselves) are logged.

Creating Claims for Players

Anyone with both griefprevention.adminclaims and griefprevention.transferclaim can create a claim for another player by first making an admin claim with /adminclaims, then running /transferclaim <player>. This is the only way to create a private claim smaller than the minimum claim size.

In GP3D you also have /makebasic (with griefprevention.adminclaims.convert) as an alternative — create the shape as an admin claim, then /makebasic to make it your basic claim, then /transferclaim to hand it to the player. Which flow you prefer is up to you.

Adjusting a Player's Claim Limit

Required permission: griefprevention.adjustclaimblocks

  • /adjustbonusclaimblocks <player> <amount> (alias /acb) — add or remove bonus claim blocks. Bonus blocks have no config cap, unlike accrued blocks.
  • /acb [myservergroups.builders] 5000 — grants 5,000 bonus blocks to everyone with the myservergroups.builders permission. This is not a one-shot: players who later gain or lose the permission also gain or lose the bonus.
  • /setaccruedclaimblocks <player> <amount> (alias /scb) — sets a player's accrued block total directly.

Investigating a Player's Claims

Required permission: griefprevention.claimslistother

/claimslist <player> lists all of a player's claims with sizes, locations, and the claim-block math.

Investigating a Specific Claim

Equip the investigation tool (stick by default) and right-click the claimed area. Shift+right-click shows nearby claims if you have griefprevention.visualizenearbyclaims. griefprevention.seeclaimsize adds size info and griefprevention.seeinactivity shows the owner's offline time on that tooltip.

Boundary Violation Alerts

GP3D addition. Piston and liquid events that get blocked at a claim boundary now notify the claim owner so they understand where the flow is being stopped — no config toggles, no per-claim water/lava permissions.

What Triggers an Alert

  • A piston tries to push a block into a claim from outside.
  • A piston inside a claim tries to push a block out of that claim into someone else's claim.
  • Water or lava tries to flow into a claim from outside it (or fails to flow out into another owner's claim).

Message Format

When the claim owner is online, they see something like:

Warning: A piston tried to enter your claim @ x:... y:... z:...!
Warning: A liquid tried to enter your claim @ x:... y:... z:...!

If several violations happen in the same burst window (~2 seconds), the plugin condenses them into a single summary line rather than spamming:

Warning: 12 liquid violations near your claim @ x:... y:... z:...!

Dedup Behavior

To keep notifications useful and not noisy, the plugin remembers recent violations and suppresses repeats:

  • Pistons: exact-location dedup. A specific piston pushing repeatedly against the same spot only alerts once per expiry window.
  • Water: 8-block radius dedup (water flows up to 7 blocks).
  • Lava (overworld / end): 5-block radius dedup (lava flows up to 4 blocks).
  • Lava (nether): 8-block radius dedup (nether lava flows up to 7 blocks).
  • Entries expire after ~5 minutes of no activity.

Why Only Alerts, No Toggles

The design intentionally avoids per-claim water/lava permission toggles. Such toggles:

  • Enable non-survival placements (holding water/lava in midair by claim boundary rules).
  • Open weird trapping cases (fake water sources held up by claim rules so players fall to their death).

Alerts solve the real problem — player confusion about where flow is happening — without opening those traps. Pistons are treated the same way: no cross-claim toggle, just better feedback.

Fighting Wilderness Grief (World Repair)

Required permission: griefprevention.restorenature

"Public grief" is damage done to the world rather than to a specific player: terrain damage, ugly builds, tree-topping (not possible with GP installed), wildfires (not possible with GP installed). /restorenature addresses the rest.

  • /restorenature (alias /rn) — right-click a block with the shovel to revert player changes in that area. Claims are respected.
  • /restorenaturefill [radius] (alias /rnf, requires griefprevention.restorenatureaggressive) — right-click at the level you want to fill to. Huge griefer craters fill in seconds.
  • /restorenatureaggressive (alias /rna, requires the aggressive permission) — removes even some natural blocks. Use carefully. Only removes blocks at and above the clicked level.

Rule of thumb: try /rn first. Only use /rna when the griefer used natural-looking blocks.

GriefPrevention does not maintain per-block history — it doesn't "roll back" in the WorldEdit sense. Instead, it identifies player-placed blocks and removes them, then smooths unnatural terrain. This is safer than regeneration because:

  • Regenerating a chunk after world-seed / worldgen changes can produce mismatched neighbors (snowy squares in deserts).
  • WorldEdit's region regen works at chunk granularity and tries to "undo" outside the selection — subtle bugs can leak.
  • Regeneration can put back things you wanted gone, like depleted dungeons and ore veins.

Always try the safe /restorenature first.

Fighting Chat Trolls

Required permission: griefprevention.softmute

Banning a troll often escalates: alt accounts, recruited friends, DDOS attempts. /softmute <player> lets the troll see their own messages (and so do other soft-muted players) while nobody else does. The troll thinks their messages are working and loses interest before escalating. Cheap, quiet, effective.

Killing Drama

Required permission: griefprevention.separate

When two players cannot get along, /separate <a> <b> forces them to ignore each other in chat without either of them knowing. /unseparate reverses it. Neat, fast, stops ambient server drama from spreading.

Reviewing Chat Logs Efficiently

Abridged social-interaction logs live under plugins/GriefPreventionData/Logs. They are formatted for human reading and auto-delete after 7 days. The config.yml log section lets you change the retention period and verbosity.

GriefPrevention3D Wiki

Getting Started

Features

Reference

Admin

Clone this wiki locally