Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 5 days ago
All versions
1.4.5
Release
1.4.5 -- Folia Bug Fixes3 months ago 14
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
š Fixed (Folia)
- Teleport crash:
onPlayerTeleportcalled the blockingEntity#teleport()from inside a Folia region-scheduled task, which always throwsUnsupportedOperationException: Must use teleportAsync while in region threading. The player was never moved and protection silently failed to apply/lift. Switched toteleportAsync(), with the follow-up state update correctly bounced back onto the owning region thread. - Entity-hiding crash risk:
EntityHider(active by default viaentities.hide-entities: true) scheduled its hide/show/spawn-hook logic on the global region scheduler instead of the region that actually owns the entity/player. Same failure class as the teleport bug ā now routed through the region-aware scheduler. - Update-notification crash risk: the "notify already-online admins of a new version" path called the raw, legacy
Bukkit.getScheduler().runTask(), which Folia rejects outright. Triggered whenever an update is detected while an admin is already online (e.g. right after/fpac reload). Now uses the Folia-safe scheduler wrapper like the rest of the plugin.
š Fixed (config correctness)
protection.pie-chart-protectionhad no effect ā tile-entity stripping (CHUNK_DATA) and entity-spawn packet cancellation ran unconditionally regardless of the setting. Both now correctly respect it.
š§ Config
config-versionbumped to4.1to ensure the migration path runs cleanly on upgrade for all existing installs.
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:NodGIhss:Bubg9ZTD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NodGIhss:Bubg9ZTD"
}

