Links
Tags
Creators
Details
0.9.14-SNAPSHOT
Compatibility
Changes
This update introduces optional ambient renewal, allowing Memento to gradually refresh unused terrain over time — while still keeping inhabited areas safe.
Nothing happens automatically until you decide to enable it.
Ambient Renewal (Optional)
Memento can now perform small renewal steps automatically during the nightly maintenance cycle.
Before this can happen, the operator must explicitly enable it:
/memento accept
This simply confirms that you understand Memento may make small changes to abandoned terrain in your world.
Until you run this command, the mod behaves exactly as before.
How nightly renewal works
Once enabled, Memento will occasionally perform a very small renewal step during the night:
• If the world has not yet been analyzed, Memento will start a scan • Once scanning is complete, it may renew one eligible region • Active or inhabited areas remain protected
Renewal remains slow, conservative, and explainable.
If you want faster progress, you can still use the manual commands.
World analysis improvements
Memento now rebuilds its understanding of the world directly from the world files, ensuring that its decisions always match the actual terrain.
This makes the system more robust and avoids potential inconsistencies.
Reminder
You can always inspect what Memento plans to do before anything happens:
/memento explain renew
This command shows where renewal could occur and why.
Feedback is always welcome. If you try the new ambient renewal feature, feel free to share your experience or open an issue on GitHub.
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:dy9kkdYI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtOQCXON:dy9kkdYI"
}

