Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published last year
Updated 3 weeks ago
All versions
0.3.2-alpha
Alpha
Complexity Analyzer 0.3.2-alpha8 months ago 21
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
๐จ Critical Fixes
- Fixed server freeze during geo-scan โ biome search no longer blocks the main server thread
- Fixed deadlock in ATOMIC scan mode โ chunk processing now uses a direct blocking method instead of cross-thread callbacks
- Fixed tick lag from
startNextTask()โ biome lookup moved to an async pipeline - Fixed tick lag from
handleRelocation()โ same async fix applied - Fixed server hang on shutdown โ chunks are now loaded synchronously on the server thread, preventing orphaned chunks that couldn't unload
- Fixed scan stalling due to short timeout โ default chunk generation timeout increased from 3โ500ms to 10 seconds
- Fixed biome search not cancellable โ thread interrupt checks added to long-running loops
- Fixed chunk duplication on repeated scans โ previously scanned coordinates are now restored from saved data before resuming
โจ New Features
- Configurable chunk timeout โ new
geo_scan.chunkTimeoutMsconfig option for tuning chunk generation wait time (useful for heavy modpacks) - Scan progress persistence โ already scanned chunk coordinates are preloaded on startup, preventing redundant work
โ๏ธ Changes
WorldScannerโ reworked threading model, added graceful shutdown supportGeoAnalysisManagerโ async task scheduling, proper shutdown sequence, scan state restorationComplexityConfigโ newgeo_scanconfiguration sectionGeoDataStorage/GeoDatabaseโ new methods for loading saved scan coordinates
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:rhPfeKXb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RQjlpUyI:rhPfeKXb"
}

