Links
Tags
Creators
Details
0.9.9-SNAPSHOT
Compatibility
Changes
This release improves scanner compatibility and significantly enhances operator diagnostics.
LZ4 Region File Support
Natural Renewal now supports LZ4-compressed region files.
If your world uses LZ4 compression internally, the scanner will now correctly read and process those chunks instead of marking them as unsupported.
This improves:
- WorldMap completeness
- Scanner convergence
- Renewal eligibility accuracy
No configuration changes required.
Expanded /memento inspect
The inspection system has been extended.
New: System-wide inspection
You can now run:
/memento inspect
Without providing a stone name.
This returns a system summary including:
- Total Witherstones and Lorestones
- Witherstone lifecycle distribution
- Renewal batch states
- Scanner activity status
- WorldMap totals (known / scanned / missing chunks)
Improved: Stone inspection
/memento inspect <name>
Now provides additional details:
- Influenced chunk count
- Renewal batch lifecycle state
- Explicit waiting explanations
- Unload blockers (e.g. players in affected chunks)
- Other entities preventing regeneration
Inspection now focuses on answering:
Why is renewal not progressing?
Improved command output
The following commands received formatting and clarity improvements:
/memento add witherstone/memento add lorestone/memento list/memento inspect/memento visualize
Changes include:
- Cleaner wording
- Structured summaries
- Bounded output for large result sets
- More consistent reporting format
Summary
Version 0.9.9 delivers:
- Broader compatibility with modern Minecraft region formats
- Deeper diagnostic visibility
- Clearer operator feedback
No gameplay mechanics changed. This is a compatibility and observability upgrade.
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:vtOQCXON:8pj3GbXk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtOQCXON:8pj3GbXk"
}

