Tags
Creators
Details
18.4.14-fabric-beta
Compatibility
Required content
Changes
GriefPrevention3D v18.4.14 — Fabric (experimental beta)
Wiki: https://github.com/castledking/GriefPrevention3D/wiki
Roadmap: platforms/fabric-common/ROADMAP.md
Still a beta, dedicated-server-only build. Back up
GriefPreventionDatabefore 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 theirPlayerData/<uuid>record alongside the accrued and bonus claim blocks. It persists across restarts./gpglow [on|off]flips the globalVisualizationGlowconfig 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 totrue) the first time they are rewritten. Old four-line records keep working and default to glow on, as on Paper. VisualizationGlowinconfig.ymlis unchanged and still defaults tofalse.
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.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:pqVXF7b5:xIfcCxtf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pqVXF7b5:xIfcCxtf"
}

