Tags
Creators
Details
18.4.10-fabric-beta
Compatibility
Required content
Changes
GriefPrevention3D v18.4.10 — Fabric (experimental beta)
Wiki: https://github.com/castledking/GriefPrevention3D/wiki
Roadmap: platforms/fabric-common/ROADMAP.md
Now a beta, dedicated-server-only build. Back up
GriefPreventionDatabefore updating. Requires Fabric API; LuckPerms is optional but recommended.
Overview
The same GriefPrevention3D.jar now runs on every Fabric release from 1.21.2 to 1.21.11 and on 26.1 through
26.3, fifteen Minecraft versions in all, and still works as a Spigot/Paper plugin. Everything from v18.4.9
works the same on the newly supported versions: claims, the claim tools, trust, the staff commands,
/transferclaim and the protections.
Minecraft 1.21.2 to 1.21.10
- 1.21.2 to 1.21.10 use the same Fabric build as 1.21.11, so the jar only grew by about 18 KB and is still around 2 MB.
- Every build boots the jar on all fifteen versions with Fabric Loader and checks it against each version's game classes.
- These versions need Java 21, as Minecraft does, and the Fabric API build for your Minecraft version.
- On 1.21.2 to 1.21.10, claims follow the server's
pvpsetting inserver.properties. From 1.21.11 on, the per-worldpvpgame rule decides. - Copper golem statues need build trust on the versions that have them (1.21.9 and later).
Not on Fabric yet
Fabric 1.21.1 and older; subdivisions, 3D and shaped claims; /restrictsubclaim, /claim alerts,
/trapped and /siege; restore nature; and buying or selling claim blocks. The roadmap lists the
protections still to come.
Upgrade notes
- Claims and player data use the same
GriefPreventionDataformat as Paper on every supported version; nothing to migrate.
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:orcI6iaw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pqVXF7b5:orcI6iaw"
}

