Links
Tags
Creators
Details
0.2.0+1.21.11
Compatibility
Changes
Fixed
- Container items now export correctly. (BUG-1 in
KNOWN_BUGS.md) - Redstone components and other stateful blocks now export with their correct state.
- Biome and light data are now included correctly in chunk exports.
- Performance and memory issues in the caching and serialization processes have been comprehensively addressed:
- Reduced blocking of the rendering/game threads caused by large-scale block capture before export, preventing noticeable stuttering caused by synchronous serialization.
- Fixed an issue where container caches were not cleaned up synchronously when blocks expired, and modified the storage to be isolated by dimension to reduce memory growth after prolonged operation.
- Cleaned up entity data that was out of sync with the block cache to prevent the continuous accumulation of entity cache data after dimension switching or frequent exports.
- Tightened concurrent access paths for mirror mapping configurations to reduce the risk of race conditions between background exports and foreground configuration reads/writes.
Added
-
SQLite chunk database (
data/world_mirror.sqliteinside each mirror world folder).
Replaces thechunkUpdateTimesfield inworldmirror_meta.jsonfor chunk dirty-tracking. The database also introduces anupdate_sourcespriority table that lets World Mirror and third-party tools (map renderers, importers) coexist without overwriting each other's data. SeeDATABASE.mdfor the schema and integration guide. -
Automatic migration of legacy
chunkUpdateTimesdata fromworldmirror_meta.jsonto SQLite on the first export after upgrading. The JSON field is removed from the file after migration. -
GitHub Actions release workflows (manual trigger):
release-modrinth.yml— builds and publishes to Modrinth.release-github.yml— builds and creates a GitHub Release with bundled JAR.
-
KNOWN_BUGS.md— documents confirmed issues and their status. -
DATABASE.md— English documentation for the SQLite schema, intended for third-party tool authors.
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:9iTjIm4a"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RjnX4gR2:9iTjIm4a"
}

