Tags
Creators
Details
1.4.9
Compatibility
Required content
Changes
š Bug Fixes
-
[Folia] Entity hiding now actually works on Folia ā On Folia servers,
hideEntity()/showEntity()calls were silently failing due to region-thread ownership violations. The plugin was scheduling visibility tasks on the region that owns the spawned entity, then attempting to mutate every online player's state from that thread ā which Folia correctly rejects. The exceptions were being swallowed silently (logged at.fine(), invisible by default), making it appear as if "nothing happened." Entity hiding is now dispatched through Folia'sEntityScheduleron a per-player basis, which always runs on the correct region thread for that player regardless of where they are in the world. -
[Folia] Entity hiding after teleport now scans the correct location ā
entityHider.updateFor()was being called beforeteleportAsync()completed, causing it to check for nearby entities around the player's pre-teleport position. Entities near the teleport destination were never hidden. The call is now correctly placed inside thewhenCompletecallback, after the teleport has landed. -
[Folia] Entities now re-show correctly when protection deactivates ā
entityHider.updateFor()was only invoked when arming protection (going underground), not when disarming (coming back up or dismounting a vehicle below protectionY). This caused entities hidden by EntityHider to remain invisible until an unrelated state change happened to trigger an update. Both arm and disarm paths now callupdateFor(). -
Hide/show failures are now visible in console ā
hideEntity()andshowEntity()errors were previously logged at.fine()(suppressed by default), masking failures entirely. They are now logged at.warning()level so server admins can see if something goes wrong.
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:aoBjOtu6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NodGIhss:aoBjOtu6"
}

