Tags
Creators
Details
1.11.0
Compatibility
Required content
Changes
What's Changed
- Add 26.3 Fabric/NeoForge
- Add 26.2 NeoForge
- Fully unhooked the Cull Thread from the Entity gamelogic (see below)
- Fix NeoForge not using the getRenderBoundingBox method for BlockEntities
- Add getRenderBoundingBox method for fabric. Fix #313
- Fix debug flag confusion
- Formatting, optimize icon #309
- Create en_ud.json by @Fhilips613 in https://github.com/tr7zw/EntityCulling/pull/310
- Update id_id.json by @nunoguevara in https://github.com/tr7zw/EntityCulling/pull/308
- Respect name display distances for culled entities by @artegoser in https://github.com/tr7zw/EntityCulling/pull/316
- All builds <= 1.12.2 got moved into a repo located at https://github.com/tr7zw/Legacy_EntityCulling
New Contributors
- @nunoguevara made their first contribution in https://github.com/tr7zw/EntityCulling/pull/308
- @artegoser made their first contribution in https://github.com/tr7zw/EntityCulling/pull/316
Note
This release contains a bunch of reworks around extracting the required (block)entity data on the main thread to prevent crashes with some other mods that can't handle the async looking up of data. These "correctness" fixes come at the cost of performance in the main client tick, so it is a tradeoff. In my tests, during reasonable conditions, this should take under 1ms every 5 ticks (250ms), up from ~0.5ms in the last release. This should be fine but needs general testing to better understand the impact. If you are experiencing issues, get in contact via GitHub/Discord. In case you are feeling adventurous and have a mod configuration that isn't impacted by these async access crashes, there is a safeMode flag in the config file to move all the lookups away from the main thread, removing all the overhead.
Full Changelog: https://github.com/tr7zw/EntityCulling/compare/1.10.5...1.11.0
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:NNAgCjsB:Wn7jtvAy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NNAgCjsB:Wn7jtvAy"
}

