Links
Tags
Creators
Details
0.9.17-SNAPSHOT
Compatibility
Changes
This release completes the core of Natural Renewal.
Memento is now feature complete. The system behaves as intended, and the focus now shifts to testing, stability, and polishing the user experience.
What this means
Natural Renewal is now fully implemented and stable:
- Areas where players spend meaningful time are preserved
- Areas outside those regions can be regenerated
- Regeneration uses the current world generator
The system now behaves consistently and predictably across different worlds.
More reliable world understanding
Memento now keeps its world knowledge up to date without forcing chunk loads.
- Changes in player activity are picked up naturally over time
- Decisions are based on current data, not outdated observations
- The system converges as the world is explored
Safe and controlled renewal
Renewal now follows a strict and consistent model:
- Regions are checked before execution
- They are checked again right before regeneration
- Loaded regions are skipped
This ensures that regeneration only happens when the world already allows it.
Clear and explainable behavior
The system is now easier to understand and reason about:
- What you see in
/memento explainmatches what will happen - Renewal is gradual and predictable
- You remain in control at all times
Documentation update
Documentation has been aligned with the actual behavior of the mod:
- Clearer explanations of how renewal works
- More precise wording of key concepts
- Improved structure and navigation
What comes next
With the core complete, the next phase is:
- testing in real worlds
- refining edge cases
- improving clarity and usability
Summary
Memento is now ready for broader use.
- The system is complete
- The behavior is stable
- The world evolves naturally
From here, we focus on making the experience smooth and reliable.
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:slDu6BGb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtOQCXON:slDu6BGb"
}

