Tags
Creators
Details
1.0.0
Compatibility
Required content
Changes
WorldBinder 1.0.0
WorldBinder 1.0.0 is the first stable public release of WorldBinder.
This release focuses on large capture reliability, durable chunk caching, recovery stability and safer exporting.
The biggest change is the durable chunk cache system. Captured chunk block data is now stored in a temporary cache while capturing, which makes large world exports much more reliable and prevents missing or empty chunks in bigger captures.
What changed?
Durable chunk cache
WorldBinder now stores completed chunk block data in a temporary cache under:
saves/WorldBinder/.cache/
This helps protect captured block data during large sessions and makes exports much safer when capturing thousands of chunks.
Temporary cache data is deleted automatically after a successful export. If Minecraft crashes or an export fails, the cache can stay available for recovery.
Large capture reliability
WorldBinder 1.0.0 fixes issues where large captures could produce missing, empty or incomplete chunks even though they appeared as captured in the F10 map.
Large captures should now export much more reliably.
Recovery cache reuse
Recovery saves now remember their matching cache folder.
If Minecraft crashes during a capture, WorldBinder can continue using the original cache instead of creating a new unrelated one. After a successful export or recovery deletion, the matching cache is cleaned up automatically.
Save and disconnect fixes
This release fixes save actions that could stop responding in some finish/progress flows.
Improved areas include:
- Save Now
- Finish Export
- Existing world overwrite confirmation
- Disconnect autosave
- Storage progress screens
- Recovery finalization
F10 map improvements
The F10 map now shows better chunk coordinates and supports copying the selected chunk center coordinate with Ctrl+C.
This makes it easier to teleport to or inspect captured chunks.
Resource pack export improvements
WorldBinder now tries harder to detect the currently active server resource pack, including cases where a server switches packs or reuses an already-downloaded pack from Minecraft's downloads folder.
When available, the active server pack is exported as:
resources.zip
Production cleanup
WorldBinder 1.0.0 also includes cleanup work around runtime text, language files, saved-data output and release wording.
Key improvements
- First stable public release
- Added durable chunk block cache
- Fixed large exports with missing or empty chunks
- Improved recovery after crashes
- Reused linked recovery cache folders
- Deleted cache data after successful exports
- Fixed save and finish actions
- Restored visible disconnect autosave progress
- Improved F10 chunk center coordinate display
- Added Ctrl+C chunk coordinate copying
- Improved server resource pack detection
- Improved 26.x saved-data output
- Moved remaining runtime text into language files
- Kept WorldBinder Fabric-only for Minecraft 26.1.2
Important notice
WorldBinder can only export data that the Minecraft client has actually received.
Some worlds may still be incomplete depending on the server, chunks, entities, dimensions, resource packs, custom content or selected output version.
Please only use WorldBinder on worlds, maps, builds, servers and resource packs that you own, created yourself, administer, or where you have explicit permission.
Feedback
Bug reports, ideas and feedback are very welcome.
GitHub: https://github.com/Philiipp06/WorldBinder
Issues: https://github.com/Philiipp06/WorldBinder/issues
Discord: https://discord.com/invite/V7h3vaXxDZ
Helpful reports include screenshots, logs and exported test worlds where possible.
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:1PpMOGQ0:4NIH1kRE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1PpMOGQ0:4NIH1kRE"
}

