Tags
Creators
Details
0.9.1-alpha-1.21.1
Compatibility
Changes
Complexity Analyzer v0.9.1 introduces under-the-hood scan stability improvements, centralized thread management, and reflection caching to eliminate background task stalls during world analysis.
๐ฅ What's New for Server Admins
- Adaptive Biome Scanning: Reconnaissance scans now actively track search stagnation and automatically abandon unreachable biomes after repeated failed relocations, preventing world scanning tasks from getting stuck in infinite loops.
โก Performance & Stability
- Thread Pool Management (
ThreadPoolManager): Switched scan executors andDataRefinerfrom unconstrained virtual thread executors to centralized compute and ForkJoin thread pools, preventing thread bloat and stabilizing CPU scheduling. - Recipe Reflection Caching (
MachineTypeUnwrapper): Cached zero-argument recipe getter lookups usingClassValue, significantly reducing reflection overhead when discovering machine recipe types. - Scan Memory Optimization (
ScanSession): Migrated attempted chunk coordinate tracking to primitive fastutil sets, cutting RAM usage and GC churn during large-area scans. - Localization Cleanup (
ServerLanguage): Simplified server-side translation resolution to use vanilla translatable fallbacks, reducing unnecessary string formatting allocations. - Internal Refactoring: Cleaned up unused recipe inspector hooks in
StandardRecipeMethodsand removed redundant session counters.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| complexityanalyzer-0.9.1-alpha-1.21.1-sources.jar | Unknown | 1.1 MiB |
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:RQjlpUyI:3eymeBTt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RQjlpUyI:3eymeBTt"
}

