Tags
Creators
Details
1.1.0
Compatibility
Required content
Changes
WorldBinder 1.1.0
WorldBinder 1.1.0 adds support for Minecraft 26.2.
This is the next stable release after WorldBinder 1.0.0. The 1.0.0 release focused on stabilizing large captures, durable chunk caching, recovery reuse and export reliability. Version 1.1.0 moves that stable foundation forward to the Minecraft 26.2 release line.
What changed?
Minecraft 26.2 support
WorldBinder is now updated for Minecraft 26.2 on Fabric.
Updated areas include:
- Gradle Minecraft target version
- Fabric metadata dependency range
- Current target-version handling
- README and HOW_TO_USE documentation
- Public about/version text
- Release metadata for 1.1.0
Version updated to 1.1.0
This release uses version 1.1.0 instead of 1.0.1 because Minecraft 26.2 support is a new compatibility release line, not just a small hotfix for 1.0.0.
Stable 1.0.0 systems kept
WorldBinder 1.1.0 keeps the major stability work from 1.0.0, including:
- Durable chunk block cache for large captures
- Fixed missing, empty or broken chunks in large exports
- Cache-backed recovery reuse after crashes
- Automatic temporary cache cleanup after successful exports
- Fixed save and disconnect autosave progress flows
- Improved F10 chunk center coordinates
- Ctrl+C chunk center coordinate copying
- Improved server resource pack detection
- German and English language support
Recommended setup
- Minecraft 26.2
- Fabric Loader 0.19.2 or newer
- Fabric API 0.152.0+26.2 or newer
- Java 25 or newer
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.
Optional dependencies
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:vMS44pai"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1PpMOGQ0:vMS44pai"
}

