Links
Tags
Creators
Details
0.9.12-SNAPSHOT
Compatibility
Changes
This release improves reliability, clarity, and operator trust in natural renewal.
No gameplay mechanics were changed, but the renewal pipeline and command behavior have been cleaned up and hardened.
🔎 Clearer Explain → Do Workflow
/memento explain renewaland/memento do renewnow operate from the same stable candidate view.- No more preview drift between “what would renew” and “what actually renews”.
do renewprocesses candidates in a controlled, bounded way.
The system is now easier to reason about and safer to operate.
🛡 Improved Region Pruning Safety
Region-based renewal has been hardened:
- Preflight checks before file operations
- Continue-on-failure behavior (one failure does not abort the entire batch)
- Clear, calm operator feedback in edge cases
- Explicit file paths shown if manual action is required
The goal is predictable, explainable behavior — even in rare failure scenarios.
đź§ Internal Memory Model Alignment
Under the hood, the renewal model has been clarified:
- World “memory” is now consistently described in terms of memorability and forgettability.
- Renewal candidates are selected cleanly from this memory model.
- Logging and CSV exports were updated to reflect this.
No changes to how renewal works — just clearer structure and better long-term maintainability.
⚠️ Automation Status
Full automatic nightly renewal remains intentionally disabled.
Before enabling automation, the following safeguards will be completed:
- Durable protection against renewal loops
- Additional guarantees around renewal safety on highly active servers
Stone-based renewal remains fully supported and stable.
âś” What Did Not Change
- Witherstone and Lorestone mechanics
- Natural renewal behavior
- Command syntax
- World compatibility
This release strengthens the foundation for safe, explainable world evolution without altering your gameplay experience.
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:89KOxPkw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtOQCXON:89KOxPkw"
}

