# 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.
Optional dependencies
VaultUnlocked
Any compatible version
QuickShop-Hikari
Any compatible version
PlaceholderAPI
Any compatible version
Developer information
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle.
maven { name = "Modrinth"; url = "https://api.modrinth.com/maven" }
