Tags
Creators
Details
1.6.3
Compatibility
Required content
Changes
WorldBinder 1.6.3 – Hotfix for Minecraft 26.3 exports
One Fabric jar for Minecraft 26.1, 26.1.1, 26.1.2, 26.2 and 26.3.
Fixes
- Blocks are exported again for 26.3: Minecraft 26.3 changed the chunk block-state format; exports now use the new format. Before, 26.3 exports loaded with only entities and no blocks – also when capturing older servers through ViaFabric.
- Server resource pack is offered again: exports store it at
resourcepacks/resources.zip, where Minecraft 26.x looks for it. - No more experimental-settings warning: exports define Overworld, Nether and End;
stopwatches.datuses the correct format.
Map fixes
- Grass under barrier layers no longer appears as gray stone on the radar, F10 map and 3D view: blocks without a map color (barriers, light, glass …) are looked through like on a vanilla map.
- New Layers > Invisible blocks toggle to show barriers, light blocks and structure voids.
Repair old exports
Select an export from 1.6.0–1.6.2 in the archive list (F9) and click Export again to rebuild it from its stored archive. The original folder is kept.
Compatibility and limits
Requires Fabric Loader 0.19.5+, Java 25 and Fabric API matching Minecraft 26.1–26.3. Mod Menu is optional. Existing configs load unchanged. WorldBinder still archives only data received by the client; movement assistance is meant for local worlds or servers that expressly allow it.
Feedback: https://github.com/Philiipp06/WorldBinder/issues Discord: https://discord.com/invite/V7h3vaXxDZ
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:JPQPWiwN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1PpMOGQ0:JPQPWiwN"
}

