Tags
Creators
Details
Beta-V1
Compatibility
Required content
Changes
WorldBinder Beta 1
WorldBinder Beta 1 is the first Beta release of WorldBinder and a major release-readiness update after the Alpha V1, Alpha V2 and Alpha V3 testing phases.
This release focuses on stabilizing the Fabric release direction, cleaning up public documentation, improving the exported world folder structure, consolidating export notes and preparing WorldBinder for wider testing as a Beta project.
Highlights
- Moved WorldBinder to a clear native Fabric-only release direction
- Removed unused multi-loader build tasks and compatibility placeholders
- Stabilized the 26.x export layout for vanilla and server import workflows
- Improved exported world structure with server-friendly root folders
- Added modern dimension mirrors for newer Minecraft versions where useful
- Improved
level.dat_old,icon.pngand saved-data output handling - Consolidated old export text files into a single export
README.md - Removed outdated loose export notes such as
SERVER_IMPORT_NOTES.txt - Improved export validation output for release-ready world saves
- Added modular export README and saved-data writer logic
- Updated README and HOW_TO_USE for the Beta 1 release
- Updated public metadata and language text from Alpha wording to Beta 1
- Kept the improved responsive WorldBinder GUI system from Alpha V3/V4
- Kept polished F9 Control Center, F10 Map, Capture, Config, Profiler and progress screens
Fabric-only release direction
WorldBinder Beta 1 is a native Fabric release.
The project is built around Fabric's client-side APIs, including its initialization, keybind, HUD, tick and mod integration systems. Because of this, WorldBinder does not currently support NeoForge, Forge or Quilt.
Other loaders may be evaluated again in the future, but Beta 1 is focused on providing the best possible Fabric experience instead of shipping incomplete multi-loader support.
Export improvements
Beta 1 improves the exported world structure to be cleaner, more predictable and easier to use.
Exports now include a more release-ready folder layout, improved saved-data output, level.dat_old, icon.png, modern dimension mirrors where appropriate and a single export README.md with important usage notes.
The goal is to make exported worlds easier to open in vanilla Minecraft and easier to import into server setups such as Paper or Multiverse-style workflows.
Responsive interface
WorldBinder keeps the improved virtual scaled GUI system introduced during the Alpha V3 cycle.
The F9 Control Center, F10 Map, settings, capture screens, profiler and progress screens are designed to remain readable and usable across different Minecraft window sizes and GUI scales.
Very small windows may still appear more pixelated because Minecraft's pixel-style UI is being scaled down, but the layout should remain consistent and usable.
Key features
- Client-side world capture
- HotCache-first chunk capture
- Vanilla world export
- Target output version selection
- Block, block entity and entity export
- Map, stats and advancement export where available
- Server resource pack export as
resources.zip - Recovery and autosave tools
- Configurable performance presets
- F9 Control Center
- F10 live chunk map with coverage view, filters and inspector tooltips
- Queue Dashboard / Profiler
- Dedicated WorldBinder keybind category
- German and English language support
Important Beta Notice
WorldBinder is still a Beta project.
Exports may still differ from the original server-side world depending on what the client received, server setup, custom content, resource packs, entities, dimensions, chunks, gamerules and the selected target output version.
WorldBinder can only save data that the client actually receives. Server-side-only logic, unloaded chunks, hidden data or data never sent to the client cannot be reconstructed perfectly.
Responsible use
Only use WorldBinder on worlds, servers, maps, builds and resource packs that you own, administer, created yourself, or where you have explicit permission to archive or export the content.
You are responsible for how exported data is used. WorldBinder does not grant rights to copy, redistribute or publish content owned by other people, servers or projects.
Feedback and bug reports
Please report bugs, ideas and feedback here:
- Repository: https://github.com/Philiipp06/WorldBinder
- Issues: https://github.com/Philiipp06/WorldBinder/issues
Useful reports include:
- Minecraft version
- WorldBinder version
- Selected target output version
- Window mode and GUI scale if the issue is UI-related
- What was captured
- What went wrong
- Screenshots, logs or exported test worlds if possible
Release status
WorldBinder Beta 1 is intended for public Beta testing and feedback.
It is a major step forward from the Alpha releases, especially around release structure, Fabric focus, export layout, documentation and overall usability, but it is still not considered a final stable 1.0 release.
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:w4a4ItfE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1PpMOGQ0:w4a4ItfE"
}

