Tags
Creators
Details
All versions
1.6.1-1.19.4
Release
Optidum 1.6.1 (1.19.4)2 weeks ago 1
Compatibility
Minecraft: Java Edition
1.19.x
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Changes
Optidum 1.6.1 - GC Elimination and Zero-Allocation FPS Boost
Performance and Memory Optimizations
- Eliminated System.gc() Anti-Pattern: Removed forced full Stop-The-World garbage collection on dimension switch and high memory pressure. Replaced with non-blocking cache eviction and adaptive throttling to eliminate frame freezes.
- Active Memory and Cache Lifecycle Manager: Modular memory trim callback system. Proactively discards stale player tracking data, border crossing records, and level caches on dimension changes (DIMENSION_CHANGE) or critical heap pressure (CRITICAL).
- Zero-Allocation Hot-Loop Reflection: Overhauled EntityTickOptimizer to use ClassValue metadata caching. Resolves entity classification (hostile, animal, ambient) and reflection handles (getTarget, hurtTime, getId, getX, getZ) once per class. Completely eliminated Class.getMethods() array cloning and string parsing allocations in the tick loop.
- Adaptive Memory Pressure AI Throttling: Automatically scales mob AI reduction factor and active distance when JVM heap pressure exceeds 85%, dropping heap allocation rate without degrading gameplay.
- Configuration Options: Added adaptiveThrottlingOnMemoryPressure (true by default) and forceSystemGc (false by default, preserving optional legacy behavior).
Fixed
- Fixed unbounded reflection lookup CPU burn when checking mob target and hurt-time fields on unindexed entities.
- Fixed player tracking map reset behavior on high-population servers.
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:KymAaNrd:gngUkKBe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KymAaNrd:gngUkKBe"
}

