# GriefPrevention3D v19.0.1 **Wiki:** https://github.com/castledking/GriefPrevention3D/wiki Back up `GriefPreventionData` before updating. ## Fabric: inactive players' claims expire Fabric used to ignore `Claims.Expiration`. It now cleans up claims as the plugin does, so abandoned claims no longer pile up on long-running servers. - **`Claims.Expiration.AllClaims.DaysInactive`** (60 days by default) deletes all of a player's claims once they have been away that long. - **`Claims.Expiration.ChestClaimDays`** (7 days by default) deletes a player's only claim sooner, if it is no bigger than a new player's claim (`Claims.AutomaticNewPlayerClaimsRadius`, 4 by default, a 9×9 claim). With Fabric's default minimum area of 100 blocks, few claims are that small. - As on the plugin, one claim owner is checked every `Advanced.ClaimExpirationCheckRate` seconds (60 by default), going round every owner in turn. These players keep their claims: - anyone online; - anyone with at least `ExceptWhenOwnerHasTotalClaimBlocks` claim blocks (10000 by default), or at least `ExceptWhenOwnerHasBonusClaimBlocks` bonus blocks (5000 by default); - anyone with **`griefprevention.dontexpire`**. `griefprevention.dontexpire` works with LuckPerms even while the player is offline: their LuckPerms data is loaded for the check and released afterwards, so a grant on a group they belong to counts too. Without LuckPerms, server operators are exempt, which is the permission's default. If the check fails, the claims stay. Expired claims are deleted without the `AbandonReturnRatio` penalty, and each one is written to the server log. Other Fabric mods can keep a claim from expiring through the new `ClaimExpirationCallback`, as plugins can with `ClaimExpirationEvent`. ### When the first claims can expire Fabric learns when players were last online from `GriefPreventionData/LastSeen.yml`, which started recording in 18.4.7 (26 September 2026). Players not seen since then keep their claims, as the plugin keeps the claims of players without a last-played time. With the default 60 days, no claim can expire before late November 2026. ### New command | Command | Permission | What it does | |---|---|---| | `/checkclaimexpiry [player]` (`/claimcheckexpiry`, `/aclaim checkexpiry`) | `griefprevention.checkclaimexpiry` | Shows when the owner of the claim you stand in was last seen, when their claims expire, and what keeps them | Checking another player by name also takes `griefprevention.admin.checkclaimexpiry`, which only operators have by default, as on the plugin. ## Spigot and Paper - **Indonesian messages.** Set `GriefPrevention.Locale` to `id_ID`, or let `PerPlayerLocale` pick it for players whose client is set to Bahasa Indonesia. - bStats now reports the server software by its name (for example Paper or Purpur), from upstream GriefPrevention (#2667). ## Config New Fabric `config.yml` keys, matching the plugin. They are added to existing files on startup without changing anything you have set, and `/gpreload` rereads them: ```yaml GriefPrevention: Claims: AutomaticNewPlayerClaimsRadius: 4 Expiration: ChestClaimDays: 7 AllClaims: DaysInactive: 60 ExceptWhenOwnerHasTotalClaimBlocks: 10000 ExceptWhenOwnerHasBonusClaimBlocks: 5000 Advanced: ClaimExpirationCheckRate: 60 ``` ## Upgrade notes - **Expiration is on by default on Fabric**, as on the plugin. To keep every claim, set both `DaysInactive` and `ChestClaimDays` to `0`. - If a Fabric expiration setting cannot be read, expiration turns off and the error is logged, instead of falling back to the defaults. - `Claims.Expiration.UnusedClaimDays` and `AutomaticNatureRestoration` are not on Fabric yet. Both need restore nature, which Fabric does not have. Both versions still ship in one `GriefPrevention3D.jar`: 1.8 through the latest release on Spigot, Paper, Purpur and Folia, and 1.21.2 through 1.21.11 and 26.1 through 26.3 on Fabric.

# GriefPrevention3D v19.0.0 **Now a stable build.** One universal JAR runs as a Bukkit plugin and as a Fabric dedicated-server mod. Fabric requires Fabric API. Back up `GriefPreventionData` before updating. ## Fabric claims and commands - **Create and manage claims.** Basic and administrative claims, 2D and 3D subdivisions, claim lookup, abandonment, trust, trust lists, and staff claim management are available through the same command aliases and permission nodes as the plugin. Fabric has no economy integration, so paid claim transfers are refused unless the player has the free-transfer permission. - **Shaped claims.** Enable `GriefPrevention.Claims.AllowShapedClaims`, then use `/shapedclaims` (alias `/shapedclaim` or `/claim mode shaped`). With the golden shovel, right-click the outline's corners in order and click the first corner again to close it. The live path and finished claim both show corner nibs and boundary markers. Clicking an existing 2D claim boundary starts a reshape. - **Extend claims.** `/extendclaim <numberOfBlocks>` (aliases `/expandclaim` and `/resizeclaim`) extends or shrinks the most specific claim at your location, or the claim selected with the shovel nib. It supports 2D and 3D claims, subdivisions, and shaped outlines. - **Inspect claims.** The configured investigation tool (`STICK` by default) shows the claim at the targeted block; sneak-use it to visualize nearby claims. The golden shovel displays claim boundaries and supports claim selection. - **Resize with the scroll wheel.** `/scrollresize` previews a claim or subdivision while scrolling and applies the change on right-click. Looking down selects the bottom face of a 3D subdivision. A selected corner is range-gated to avoid a corner click registering through to a farther block. Shaped claims are disabled by default. `AllowShapedSubClaims` also defaults to `false`; `ShapedMinimumWidth` and `ShapedMinimumArea` control their size rules. `Allow3DSubdivisions` defaults to `true`. These settings are read from the existing `config.yml` and added on startup when missing. ## Claim protection - Explosions respect the configured land-claim and surface explosion protections, including protected entities. - Starting or extending a raid requires build trust in the raid-center claim, or in the triggering player's claim when the raid center is unclaimed. `Claims.RaidTriggersRequireBuildTrust` defaults to `true`. ## Compatibility and packaging - One Modrinth release lists Bukkit, Folia, Paper, Purpur, Spigot, and Fabric, using this combined changelog. - Fabric supports Minecraft 1.21.2–1.21.11 and 26.1–26.3 on dedicated servers. Bukkit-family support starts at Minecraft 1.8. - Modrinth stores one game-version list for all loaders on a release, so this listing advertises the Fabric targets. Bukkit support for older Minecraft releases remains available through Spigot and the universal JAR. - The universal JAR is about 2.2 MB, below the 5 MB target. ## Upgrade notes No claim migration is needed. Existing settings remain in place; new config keys are added with the defaults above.

# GriefPrevention3D v18.4.14 — Fabric (experimental beta) **Wiki:** https://github.com/castledking/GriefPrevention3D/wiki **Roadmap:** [platforms/fabric-common/ROADMAP.md](https://github.com/castledking/GriefPrevention3D/blob/master/platforms/fabric-common/ROADMAP.md) > **Still a beta, dedicated-server-only build.** Back up `GriefPreventionData` before updating. Requires Fabric > API; LuckPerms is optional but recommended. ## Overview Two changes land on Fabric. Minecraft 26.3's cushions, which arrived without any claim protection, are now protected like other decorations, and the new per-player glow toggle from the Paper side comes to Fabric as `/claimglow` and `/gpglow`. ## New commands | Command | Permission | What it does | |---|---|---| | `/claimglow` (`/claim glow`) | `griefprevention.glow` | Toggles glowing claim borders for this player | | `/gpglow` | `griefprevention.debug` | Toggles the global visualization glow setting | Both permissions default to `true` and `op` respectively, as on Paper. `/claimglow` only does anything while `VisualizationGlow` is on in `config.yml`. ## Cushion protection Cushions (26.3+) are entities, not blocks, so nothing protected them: any player could place or break one inside a claim, and a fishing rod could pull one out. They are now treated like armor stands and item frames: - **Melee and arrows.** Stopped before the hit lands, as with other build-protected entities. - **Snowballs and eggs.** These call `Entity.hurt()` directly and bypass the melee hook, so a separate mixin on the cushion's own damage handling catches them. - **Fishing rods.** Reeling a claimed cushion in takes container trust. - **Sitting.** Right-clicking a cushion to sit on it is allowed for everyone, matching `Claims.PreventCushionMount` (default false) on Paper. Cushions only exist on 26.3, so older releases see no change. ## Glow toggle - `/claimglow [on|off]` flips the player's own glow setting, stored in their `PlayerData/<uuid>` record alongside the accrued and bonus claim blocks. It persists across restarts. - `/gpglow [on|off]` flips the global `VisualizationGlow` config key. It is always available to admins. - The Fabric visualization now checks both the global setting and the player's, so a player who turned glow off for themselves stops seeing glowing outlines even while the server-wide setting stays on. Toggling either setting refreshes any visualization the player currently has drawn. ## Upgrade notes - Player data files gain a fifth line (`glowEnabled`, defaulting to `true`) the first time they are rewritten. Old four-line records keep working and default to glow on, as on Paper. - `VisualizationGlow` in `config.yml` is unchanged and still defaults to `false`. ## Not on Fabric yet The roadmap lists the protections still to come. Shaped claims, merging claims, `/siege`, `/extendclaim`, restore nature, buying or selling claim blocks and charging fees remain Paper-only.

# GriefPrevention3D v18.4.14 **Wiki:** https://github.com/castledking/GriefPrevention3D/wiki ## Fixes - **Claimed cushions can no longer be broken by untrusted players** ([#13](https://github.com/castledking/GriefPrevention3D/issues/13)). A cushion is an entity, not a block, so the block protection that covers everything else never applied to it. On top of that, it is a non-living entity: a hit on one raises no damage event at all, so the creature protection that covers armor stands and item frames never saw it either. All of these now need build trust in the cushion's claim: - **Paper / Purpur / Folia.** Melee, arrows, snowballs, eggs and fire all go through the cushion's break event now. Reeling one in with a fishing rod takes container trust, as with armor stands. - **Fabric.** Melee and arrows are stopped before the hit lands, and a new mixin on the cushion's own damage handling stops snowballs and eggs, which bypass the melee hook. Sitting on a cushion in a claim you can't build in is still allowed, matching `Claims.PreventCushionMount` (default false) on Paper. Reeling one in takes container trust. - **Both.** `EntityDamageHandler` no longer carries a dead `CUSHION` entry that could never fire. Cushions only exist on Minecraft 26.3 and later, so older servers are unaffected. ## New features - **Per-player glow toggle for claim visualizations.** `/claimglow` (or `/claim glow`) lets each player turn the glowing outline on or off for themselves, independently of the server-wide `VisualizationGlow` setting. The setting persists across restarts in the player data file. `/gpglow` lets an administrator flip the global setting at runtime; it is always available, while `/claimglow` only works while the global setting is on. - Paper: `/claimglow [on|off]` (`griefprevention.glow`), `/gpglow [on|off]` (`griefprevention.debug`). - Fabric: the same two commands, registered through the alias system. - Toggling either setting refreshes any visualization the player currently has drawn, so the change shows up immediately. ## Upgrade notes Nothing to migrate. The player data file gains a fifth line (`glowEnabled`, defaulting to `true`) the first time a player's data is rewritten; old four-line records keep working and default to glow on. The `VisualizationGlow` config key is unchanged. Both versions still ship in one `GriefPrevention3D.jar`: 1.8 through the latest release on Spigot, Paper, Purpur and Folia, and 1.21.2 through 1.21.11 and 26.1 through 26.3 on Fabric.

# GriefPrevention3D v18.4.13 — Fabric (experimental beta) **Wiki:** https://github.com/castledking/GriefPrevention3D/wiki **Roadmap:** [platforms/fabric-common/ROADMAP.md](https://github.com/castledking/GriefPrevention3D/blob/master/platforms/fabric-common/ROADMAP.md) > **Still a beta, dedicated-server-only build.** Back up `GriefPreventionData` before updating. Requires Fabric > API; LuckPerms is optional but recommended. ## Overview Three more Paper commands come to Fabric. `/scrollresize` resizes a claim with the mouse wheel, `/trapped` gets a player out of a claim they can't build in, and `/claim alerts` warns owners when a piston or fluid is stopped at their claim's border. Six protections come with them: ender pearls and chorus fruit, lightning fires, fishing rods, sand cannons, sword sweeps and Minecraft 26.2's sulfur cubes. The same `GriefPrevention3D.jar` still runs on Fabric 1.21.2 through 1.21.11 and 26.1 through 26.3, and as a Spigot/Paper plugin. ## New commands | Command | Permission | What it does | |---|---|---| | `/scrollresize` (`/claim scrollresize`, `/sr`, `/src`) | `griefprevention.scrollresize` | Resizes a claim or subdivision with the mouse wheel | | `/trapped` (`/claim trapped`) | `griefprevention.trapped` | Moves you out of a claim you can't build in | | `/claim alerts [on\|off]` | `griefprevention.claimalerts` | Border alerts for the claim you're standing in | | `/claimtogglealerts [on\|off]` | `griefprevention.toggleclaimalerts` | Border alerts for all your claims | All four permissions default to `true`, as on Paper. ### /scrollresize - Hold the golden shovel and stand in a claim or subdivision, or select one of its corners with the shovel first. Then run `/scrollresize`. Look at a side of the claim and scroll up to push that side away from you, or down to pull it toward you. - While you scroll, the new outline is drawn along with the claims around it. The claim's size and the claim blocks you'd have left show above the hotbar. If the new outline overlaps another claim or costs more blocks than you have, you're told right away. - Right-click to apply. The resize goes through the same checks as resizing with the shovel: minimum size, overlaps, claim blocks, and subdivisions fitting inside their parent. - If you selected a corner first, only the two sides that meet at that corner move. - Any of these cancels: left-clicking a block or entity, dropping (Q), swapping hands (F), pressing a number key, putting the shovel away, dying, changing worlds, or a minute without scrolling. Left-clicking the air doesn't cancel, because 26.3 no longer tells the server about it. - Shaped claims can't be made on Fabric yet, so they can't be scroll-resized either. ### /trapped - Stand still for ten seconds in a claim you can't build in, and you're moved past the claim's west and north corner and up to the surface, as on Paper. If another claim is in the way, you're moved past that one too. The surface you'd land on is checked against claims as well, so a 3D claim above the ground can't catch you. - Moving during the ten seconds cancels the rescue. - Overworld only, since there's no telling where a safe spot is in the nether or the end. Administrative claims only when `Claims.AllowTrappedInAdminClaims` is on. - Paper's chat hint, which points players who say "trapped" or "stuck" at `/trapped`, isn't on Fabric yet. ### Claim alerts - A claim's owner is warned when a piston tries to push a block into or out of the claim, or a fluid tries to flow in or out, and is stopped. The warning gives the location. Repeats are merged, and a burst of them is summed up in one message, as on Paper. - `/claim alerts on|off` sets the claim you're standing in. `/claimtogglealerts on|off` sets all your claims. ## New protections - **Ender pearls and chorus fruit** need access trust to land in a claim (`EnderPearlsRequireAccessTrust`). A refused pearl breaks, and comes back to the thrower when `RefundDeniedEnderPearls` is on. Players in creative never spent it, so they get nothing back. A refused chorus fruit jump is undone, and vanilla tries another spot. - **Lightning** starts no fires in claims. - **Fishing rods** need container trust to reel in a claimed animal, armor stand or sulfur cube. - **Falling blocks** (sand cannons): a falling block that drifted sideways only lands in a claim if the spot it fell from is in that claim too, or if it fell from a claim and lands in one of that claim's unrestricted subdivisions. Otherwise it drops as an item. - **Sword sweeps** get the same protection as the hit that caused them. A sweep used to damage the mobs beside its target directly, past every claim check. Creatures, villagers and armor stands in claims, and players in claims where PvP is off, are now checked like the target. On 1.21.2 to 1.21.4 the sweep's knockback is checked too. - **Sulfur cubes** (26.2+) are protected like other creatures ([#12](https://github.com/castledking/GriefPrevention3D/issues/12)). Hits, burning arrows and fire aspect can't reach a claimed cube, so a TNT cube can't be lit. Using one takes container trust. Hits were already stopped before the cube's own damage handling; the gaps were fishing rods and sweeps, both closed above. ## Config New `config.yml` keys, matching the Paper plugin. They're added to existing files on startup without changing anything you've set, and `/gpreload` rereads them. ```yaml GriefPrevention: Claims: AllowTrappedInAdminClaims: false EnderPearlsRequireAccessTrust: true RefundDeniedEnderPearls: true ``` `Allow3DSubdivisions`, which v18.4.12 read but never wrote into the file, now shows up there too. ## Stricter than Paper - On Paper, anyone standing in a claim can mute its owner's alerts with `/claim alerts`. On Fabric it takes permission to edit the claim. - `/claimtogglealerts` also covers the subdivisions of your claims. Paper leaves subdivisions as they were. ## Upgrade notes - Claims and player data keep the same `GriefPreventionData` format as Paper. There's nothing to migrate. - `EnderPearlsRequireAccessTrust` defaults to `true`, as on Paper. From this release on, players can't pearl or chorus-fruit into claims they have no access trust in. Set it to `false` to allow that again. - Sweeps, fishing rods and falling blocks now respect claims. Sand cannons aimed into claims they didn't start in stop working, and so do fishing rods used on other players' animals. - To keep players off a new command, deny its permission in LuckPerms. ## Not on Fabric yet Shaped claims and shaped subdivisions (`/shapedclaims`, `/shapedsubdivideclaims`), merging claims, `/siege`, `/extendclaim`, restore nature, buying or selling claim blocks, and charging fees. The roadmap lists the protections still to come.

# GriefPrevention3D v18.4.13 **Wiki:** https://github.com/castledking/GriefPrevention3D/wiki ## Fixes - **Sulfur cubes in claims are protected like other creatures** ([#12](https://github.com/castledking/GriefPrevention3D/issues/12)). Minecraft 26.2's sulfur cubes got past claim protection in three ways. All three now need container trust in the cube's claim, which is what hurting any claimed creature already needs: - **Hits.** A cube holding a block takes no damage from a hit. The hit knocks it away instead, and fire aspect lights a TNT cube's fuse. Neither fires a damage event, so creature protection never saw them. On Paper and servers built on it, the hit is now stopped before it lands. That covers knockback, fire aspect and a sword killing an empty cube. Spigot has no event for this, so there a hit cube is still put back where it stood, as before. - **Arrows and other projectiles.** A projectile shot by a player without container trust stops when it hits a claimed cube, so a burning arrow can no longer prime a TNT cube. - **Fishing rods.** Reeling in a claimed cube now takes container trust, as reeling in animals and armor stands already did. The protection follows `Claims.ProtectCreatures`: turn that off and sulfur cubes are no more protected than other creatures. Staff using `/ignoreclaims` get through as usual. - **New claims reach down to everything built under them.** When a claim is created, GriefPrevention looks under it for player-built blocks and storage, and lowers the claim's floor to cover them. If the claim's west or north edge was at a negative coordinate, that search skipped the chunks along that edge. Chests and builds under that part of the claim could end up below the claim's floor, unprotected. Ported from upstream GriefPrevention (#2659). 3D claims are not affected, since they keep the heights they were drawn with. ## Upgrade notes Nothing to migrate and no new options. Sulfur cubes only exist on Minecraft 26.2 and later, so older servers only get the claim depth fix. The experimental Fabric version in the same jar gains `/scrollresize`, `/trapped`, claim alerts and several new protections. They're listed in the Fabric version's changelog on Modrinth. Both versions still ship in one `GriefPrevention3D.jar`: 1.8 through the latest release on Spigot, Paper, Purpur and Folia, and 1.21.2 through 1.21.11 and 26.1 through 26.3 on Fabric.

# GriefPrevention3D v18.4.12 — Fabric (experimental beta) **Wiki:** https://github.com/castledking/GriefPrevention3D/wiki **Roadmap:** [platforms/fabric-common/ROADMAP.md](https://github.com/castledking/GriefPrevention3D/blob/master/platforms/fabric-common/ROADMAP.md) > **Still a beta, dedicated-server-only build.** Back up `GriefPreventionData` before updating. Requires Fabric > API; LuckPerms is optional but recommended. ## Overview Fabric finally has subdivisions. `/subdivideclaims` cuts a claim into pieces, `/3dsubdivideclaims` cuts it into pieces with exact heights, and both can be resized and trusted like on Paper. Everything a claim touches under water or in the air also got better: the claim tool now looks for the corner you aim at instead of whatever block the view happens to reach, so a corner sticking out of the sea is a corner you can click. The same `GriefPrevention3D.jar` still runs on Fabric 1.21.2 through 1.21.11 and 26.1 through 26.3 and as a Spigot/Paper plugin. ## Subdivisions | Command | What it does | |---|---| | `/subdivideclaims` (`/claim mode 2d`) | The shovel draws subdivisions that reach from the claim's floor to the sky, as on Paper | | `/3dsubdivideclaims` (`/claim mode 3d`) | The shovel draws subdivisions whose top and bottom you pick | | `/basicclaims` (`/claim mode basic`) | Back to whole claims | | `/restrictsubclaim` | Stops a subdivision inheriting its parent's trust, or lets it again | - Permissions `griefprevention.subdivideclaims` and `griefprevention.3dsubdivideclaims` both default to `true`, as on Paper. - Take the golden shovel into a claim you manage, right-click where the subdivision starts, right-click again where it ends. A 2D subdivision fills the height of its claim; a 3D one uses the heights you clicked, exactly. - Subdivisions may be any size, including one block, and must fit inside their parent without touching each other. Overlaps are refused with Paper's messages and a conflict zone. - Subdivisions can be resized by clicking their corner and dragged to the opposite corner, and they carry their own trust: `/trust`, `/trustlist` and the rest work on them as on Paper. - Sneaking with the shovel at a corner in subdivision mode subdivides there; without sneaking it still resizes the claim whose corner it is, exactly as on Paper. - Nested subdivisions (a subdivision inside a subdivision) are not offered yet, as on Paper without `AllowNestedSubClaims`. `/restrictsubclaim` is in this release, so trust inheritance is on the player to manage. ## Corner clicks, under water and everywhere else Both the stick and the shovel work from up to 100 blocks away. On a faraway click the tool follows the player's view, and while doing so it now also looks for the corner of a claim they are aiming at: - A 3D claim's corner is a single block, so the corner is the block the click lands on, whatever it is made of. - A claim without heights of its own — a parent claim, a 2D subdivision — has a corner that runs its whole height, so whichever block of that corner the view passes is the one clicked. The corner under water is as good as any other. This is what Paper already does, and it fixes the two ways a far corner used to fail: - Aim at a corner and get nothing: the corner is air, water or a gap, so the click reached nothing at all. - Aim at a corner and get the seabed: the click landed a block or two away, outside the claim, so a **new** claim started instead of the corner being selected for a resize. The corner only takes the click when it is what the player is closest to along their view — within two blocks of it, and within a forgiving 1.2 blocks of the corner itself — so ordinary clicks are untouched. A half-finished claim or subdivision never snaps, keeping its second corner exactly where it was clicked. ## Visualization - Fake blocks can be hit: left-clicking one of the blocks a visualization shows sends back the real block and drops it from the display, as breaking it always did. - 3D claims two blocks thick or thinner no longer draw the extra vertical corner markers. ## Config New `config.yml` key, added to existing files on startup and reread by `/gpreload`, matching the Paper plugin: ```yaml GriefPrevention: Claims: Allow3DSubdivisions: true ``` Turn it off and `/3dsubdivideclaims` answers that 3D subdivisions are disabled here, while `/subdivideclaims` keeps working. ## Upgrade notes - Claims and player data keep the same `GriefPreventionData` format as Paper; nothing to migrate. Subdivisions made on Paper in a claim you copy over are resized, trusted and abandoned as usual here. - `Allow3DSubdivisions` defaults to `true`, so 3D subdivision mode is open from this release on. - Clicks near a corner now pick that corner, at any range, instead of the block behind it. That is what Paper has always done within reach; it is only new because the range is no longer limited to what the player touches. ## Not on Fabric yet Shaped claims and shaped subdivisions (`/shapedclaims`, `/shapedsubdivideclaims`), merging claims, `/trapped`, `/siege`, `/extendclaim`, restore nature, buying or selling claim blocks, `/claim alerts` and charging fees. The roadmap lists the protections still to come.

# GriefPrevention3D v18.4.12 **Wiki:** https://github.com/castledking/GriefPrevention3D/wiki Nothing changes for Spigot and Paper servers in this release. It behaves exactly like v18.4.11, so updating is optional. This update is for the experimental Fabric version in the same jar. Fabric finally has subdivisions, including 3D ones, and its claim tool finds the corner you aim at from any distance, so a corner under water is clickable. The Fabric changes are in the Fabric version's changelog on Modrinth. Both versions still ship in one `GriefPrevention3D.jar`: 1.8 through the latest release on Spigot, Paper, Purpur and Folia, and 1.21.2 through 1.21.11 and 26.1 through 26.3 on Fabric.

# GriefPrevention3D v18.4.11 **Wiki:** https://github.com/castledking/GriefPrevention3D/wiki ## New options - **`AutoIgnoreClaims` (default false).** Staff who hold the new `griefprevention.autoignoreclaims` permission start each session with claim protections already off, so they can build wherever they need to without touching every claim first. The grant covers every protection: building, containers, entity damage, PvE and knockback, pets, and the rest. Running `/ignoreclaims` turns protections back on for the rest of that session. It is not saved to disk, so it never outlives the session. The new permission defaults to `op` and is deliberately **not** a child of `griefprevention.adminclaims`, so granting that one does not hand it out. Grant it on its own: ``` griefprevention.autoignoreclaims: default: op ``` - **`RequireIgnoreClaimsInAdminClaims` (default false).** Staff normally walk into administrative claims and build freely. With this on, building and using containers inside an administrative claim additionally requires that the staff member be ignoring claims. Walking through, resizing and managing administrative claims still work as before, so `/adminclaim` and friends do not suddenly start refusing. The refusal reads the same way every other protection refuses: each one gives its own reason for that action, followed by the usual "To override, use /ignoreclaims." pointer. No new messages were needed for it. The two options pair up: turn `RequireIgnoreClaimsInAdminClaims` on and give your builders `griefprevention.autoignoreclaims` alongside `AutoIgnoreClaims`, and staff keep building in admin land while every other claim stays protected. Both options appear in your generated `config.yml` between `AdminsGetSignNotifications` and `VisualizationAntiCheatCompatMode`, in this order: ```yaml GriefPrevention: AdminsGetSignNotifications: true AutoIgnoreClaims: false RequireIgnoreClaimsInAdminClaims: false VisualizationAntiCheatCompatMode: false ``` ## Upgrade notes Nothing to migrate. Both options are off by default, so nothing changes until you turn one on. Staff without `griefprevention.autoignoreclaims` are unaffected by `AutoIgnoreClaims` even when it is on. ## Under the hood - The session grant is a separate field on a player's data from the `/ignoreclaims` toggle, and like that toggle it is never written to storage. Protection checks ask whether a player is ignoring claims rather than reading the toggle directly, so every existing protection honours the session grant without each one needing to know about it. - The two `/ignoreclaims` code paths, the unified command handler and the legacy one, now share a single toggle so they cannot drift apart. - New tests cover the session grant, the permission gate, `/ignoreclaims` turning protections back on, and the administrative claim requirement for building and containers.

# GriefPrevention3D v18.4.11 **Wiki:** https://github.com/castledking/GriefPrevention3D/wiki ## New options - **`AutoIgnoreClaims` (default false).** Staff who hold the new `griefprevention.autoignoreclaims` permission start each session with claim protections already off, so they can build wherever they need to without touching every claim first. The grant covers every protection: building, containers, entity damage, PvE and knockback, pets, and the rest. Running `/ignoreclaims` turns protections back on for the rest of that session. It is not saved to disk, so it never outlives the session. The new permission defaults to `op` and is deliberately **not** a child of `griefprevention.adminclaims`, so granting that one does not hand it out. Grant it on its own: ``` griefprevention.autoignoreclaims: default: op ``` - **`RequireIgnoreClaimsInAdminClaims` (default false).** Staff normally walk into administrative claims and build freely. With this on, building and using containers inside an administrative claim additionally requires that the staff member be ignoring claims. Walking through, resizing and managing administrative claims still work as before, so `/adminclaim` and friends do not suddenly start refusing. The refusal reads the same way every other protection refuses: each one gives its own reason for that action, followed by the usual "To override, use /ignoreclaims." pointer. No new messages were needed for it. The two options pair up: turn `RequireIgnoreClaimsInAdminClaims` on and give your builders `griefprevention.autoignoreclaims` alongside `AutoIgnoreClaims`, and staff keep building in admin land while every other claim stays protected. Both options appear in your generated `config.yml` between `AdminsGetSignNotifications` and `VisualizationAntiCheatCompatMode`, in this order: ```yaml GriefPrevention: AdminsGetSignNotifications: true AutoIgnoreClaims: false RequireIgnoreClaimsInAdminClaims: false VisualizationAntiCheatCompatMode: false ``` ## Upgrade notes Nothing to migrate. Both options are off by default, so nothing changes until you turn one on. Staff without `griefprevention.autoignoreclaims` are unaffected by `AutoIgnoreClaims` even when it is on. ## Under the hood - The session grant is a separate field on a player's data from the `/ignoreclaims` toggle, and like that toggle it is never written to storage. Protection checks ask whether a player is ignoring claims rather than reading the toggle directly, so every existing protection honours the session grant without each one needing to know about it. - The two `/ignoreclaims` code paths, the unified command handler and the legacy one, now share a single toggle so they cannot drift apart. - New tests cover the session grant, the permission gate, `/ignoreclaims` turning protections back on, and the administrative claim requirement for building and containers.