All versions
1.1.0
Release
Lazy Chunk Load 1.1.04 months ago 16
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Server-side
Singleplayer
Changes
Lazy Chunk Load Changelog
1.1.0 β 2026-06-17
π New Features
- Stepped CPU Throttling: Main chunk loading now dynamically adjusts its frequency based on CPU usage. Full speed below 85% CPU, progressively slowing down between 85%~100%. At worst, chunks are processed every 0.2s β terrain never gets stuck.
- Preloading Enabled by Default: Background preloading is now on by default. Idle players will have surrounding chunks generated automatically.
- Priority-Based Preloading: Chunks are prioritized by three weighted scores β distance (closer first), look direction (ahead first), and aging (long-unloaded first). Chunks under your feet and in front of you load first.
- F3 Debug Overlay: Press F3 to see CPU usage, chunks loaded per tick, throttle status, and preload state at the bottom-left of the screen.
- Warmup Protection: No throttling for the first 10 seconds after joining a world, ensuring spawn chunks load quickly.
- Save Safety: Preloading and throttling are automatically paused during world saves to prevent conflicts.
- Emergency Pass-Through: If a player steps into an unloaded chunk, all limits are bypassed β the chunk loads immediately.
- VulkanMod Compatible: F3 overlay silenty disables itself when VulkanMod is present. Core functionality is unaffected.
π§ Optimizations
- CPU polling uses a 1-second cache (down from once per tick), virtually zero overhead
- Preload queue periodically prunes already-loaded chunks to prevent memory bloat
- Preloading auto-pauses during player movement to avoid competing for CPU
β Removed
- Removed
/lazychunkloadcommands to avoid server permission issues - All settings now managed via
config/lazychunkload.jsonandconfig/lazychunkload-runtime.json
π¦ Supported Platforms
| Platform | Version |
|---|---|
| Fabric | 1.21.x |
| Forge | 1.20.1 |
1.0.0 β 2026-06-14
- Initial release
- Basic CPU monitoring and throttling
/lazychunkload status/tipscommands
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:ZsyQkd1s:2xgxIsMw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZsyQkd1s:2xgxIsMw"
}

