Links
Tags
Creators
Details
0.9.11-SNAPSHOT
Compatibility
Changes
Description
Natural Renewal is now live.
With this release, /memento renew force performs actual world renewal.
This is the first version where Memento modifies region data directly.
What This Means
Memento now supports two renewal paths:
π Region-Based Pruning (Primary Path)
If a full region is conservatively determined to be forgettable, Memento will:
- Remove the region file
- Remove the matching entity file
- Remove the matching POI file
When players later revisit that area, Minecraft regenerates it naturally using current world generation.
This is ideal for remote, long-abandoned terrain.
π§± Chunk-Based Renewal (Fallback)
If a region is not fully eligible, eligible chunks are scheduled through the existing renewal engine.
This is useful near inhabited areas where selective renewal is required.
How It Works
- Renewal eligibility is evaluated at command time from a stable projection snapshot.
- Evaluation is region-first, with chunk fallback only when needed.
- Spatial checks are bounded and region-aware (no world-wide scans).
- File operations are staged and guarded to reduce risk.
- Only one pruning operation runs at a time.
The system is conservative by design: unknown or active evidence blocks region-level pruning.
β οΈ Important β Back Up Your World
This version performs real file removal.
Safeguards are in place, but this is the first active implementation of Natural Renewal.
Back up your world before testing.
Performance Improvements
Projection analysis is now significantly faster due to bounded spatial evaluation. Large worlds benefit the most from this change.
Temporary Operator Message
An operator-facing message tracking eligibility recomputation is intentionally enabled in this release to aid testing. It will be removed in a follow-up version.
How to Test
Recommended test approach:
- Back up your world.
- Run
/memento renewto review eligibility. - Run
/memento renew forcein remote areas first. - Revisit pruned regions to confirm natural regeneration.
- Observe behavior near inhabited areas.
Test across different dimensions if possible.
Reporting Issues
If you encounter problems:
- Provide logs (
latest.logordebug.log) - Mention world size and dimension
- Describe command sequence used
- State whether region or chunk renewal was selected
Please report issues on GitHub: π https://github.com/olilanz/memento/issues
This release marks the transition from analysis-only to true, automatic world evolution.
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:yec3DYXB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtOQCXON:yec3DYXB"
}

