Tags
Creators
Details
19.0.2
Compatibility
Required content
Changes
GriefPrevention3D v19.0.2
Wiki: https://github.com/castledking/GriefPrevention3D/wiki
Back up GriefPreventionData before updating.
Weaving protection on Paper and Fabric
Weaving could create cobwebs inside another player's claim when an affected player or mob died. This update protects those placements on Paper, Purpur, Folia and Fabric.
- Player deaths require build trust. Every prospective cobweb is checked at the block where it would appear. Dying outside a claim can no longer place webs across its boundary. Subdivision restrictions and 3D height boundaries are respected, and authorized claim bypass still works.
- Mob deaths cannot place cobwebs inside claims. The death does not reliably identify who applied the weaving effect, so claimed blocks are protected regardless of the mob's type. Weaving still works in survival wilderness and in worlds where claims are disabled.
- Claimed animals and villagers require container trust to receive weaving potions. Access trust alone is insufficient. This covers splash potions and both standard and custom lingering weaving effects.
- Dispensers cannot apply weaving across claim boundaries. They may affect creatures in the same claim as the dispenser, including the same subdivision. A neighboring claim is treated separately even when it has the same owner. Fabric remembers the dispenser's launch location and carries it into the lingering cloud, so the potion's landing position cannot bypass this check.
Players may still drink weaving potions and receive their own thrown potion effects. Any cobwebs generated by their death follow the build-permission checks above. Other potion effects are unchanged.
The Fabric protection runs in both bundled adapters, covering Minecraft 1.21.2–1.21.11 and 26.1–26.3.
Upstream updates
- Removed the obsolete conversion of player names to UUIDs, following upstream GriefPrevention. MySQL support and migration from flat files to the database remain available in GP3D.
- Synced upstream's knockback-listener cleanup. GP3D retains its existing handling, which already avoids processing the same entity knockback twice.
Upgrade notes
- No new config keys or permission nodes are needed. Existing claims, trust and UUID-based data keep working.
- Mob-based cobweb farms inside claims will stop placing webs. Mob-generated cobwebs remain allowed in survival wilderness; player-generated webs in claims require build trust.
- Servers whose GP data still uses pre-UUID player names must first update through an older release that performs that conversion, then update to 19.0.2.
Both platforms continue to ship in one universal GriefPrevention3D.jar. Fabric requires Fabric API.
Optional dependencies
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:lEvsiZaa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pqVXF7b5:lEvsiZaa"
}

