Links
Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 2 weeks ago
All versions
0.3.0+26.2-fabric
Alpha
World Mirror 0.3.0+26.2-fabric2 weeks ago 77
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Changes
Added
- Fabric builds for Minecraft
1.21.11,26.1.2, and26.2from one shared source layout. - Optional integration with Xaero World Map Bridge
0.1.0, including World Mirror chunk-status rendering on Xaero's fullscreen map without embedding the bridge in World Mirror's jar. scripts/build-modrinth.ps1builds all Fabric targets and collects the three current-version distributable JARs inbuild/modrinth.- Per-world mirror-location migration with confirmation, synchronized path remapping, and safeguards that require downloads and exports to stop first.
- A vanilla-readable
worldmirror_environmentdata pack embedded in each mirror save, with featureless per-dimension biomes for uncaptured void terrain. - Read-only detection of the currently-open local mirror save, including its schema compatibility and original source identity.
- Enter-before-load schema updates for outdated local mirror saves, with a targeted backup, native confirmation, progress, and completion feedback.
- Metadata lineage choices for Nearby Export made from an open mirror: inherit the original source, point at the current mirror, or create an independent snapshot.
Changed
- Migrated the Java package namespace to
io.github.billstark001.worldmirror. - Replaced LibGui/Cotton status UI with native Minecraft screens while retaining source, mirror location, download/export state, per-world settings, and conflict-management views.
- The built-in map and Xaero overlay now use asynchronous status snapshots, viewport aggregation, and merged state-coloured boundaries.
- Compact status layout: source/type with mirror and cache count with last-sync time share rows; output and Xaero-bridge status are in the per-world settings tab.
Fixed
- Status-screen text now uses opaque ARGB colours on the new GUI extraction API.
- Avoided forced immediate screen rendering when opening the status UI, eliminating the opening black flash.
- Restored state-coloured chunk boundaries on built-in and Xaero map overlays.
- Completed four-locale UI coverage for status ages, migration feedback, nearby-export messages, and chunk-map tooltips.
- Migrated existing mirrors from the flat
the_voidgenerator before exporting more chunks, preserving exported chunk palettes while restoring normal Overworld, Nether, and End climate baselines for uncaptured space. - Kept data-pack asset revisions separate from the semantic world-generation schema so Minecraft command/data-pack format changes can refresh assets without redefining the migration contract.
- Added metadata to new Nearby Export saves and made the status map use a currently-open mirror save's own capture database; Xaero shows a yellow current-mirror indicator where its canvas API permits.
- Prevented an older mod from overwriting a mirror's newer worldgen schema or embedded-asset revision.
- Replaced silent download-time schema migration with explicit confirmation; current mirror saves are only warned about capture when Download is clicked, not when entered.
- Replaced Xaero's obscured yellow dot with a high-contrast
WMUI badge beside its settings button and a one-time explanatory toast. - Deferred the World Mirror schema prompt until Minecraft's own save-version upgrade has completed, and restored the world list correctly when that prompt is cancelled.
- Refreshed migrated metadata with the currently loaded mod version and repaired generated data-pack metadata for Minecraft's required
min_format/max_formatrange. - Added a one-time, backed-up cleanup for blank legacy
minecraft:the_voidchunks so they regenerate under schema 1 without deleting captured or player-modified terrain. - Stopped schema migration from writing Minecraft's exclusively locked
session.lockfile.
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:RjnX4gR2:kzf3M9W7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RjnX4gR2:kzf3M9W7"
}

