Links
Tags
Creators
Details
0.9.15-SNAPSHOT
Compatibility
Changes
This release improves the reliability of world analysis, especially for larger worlds, and introduces the first internal regression test suite protecting this part of the system.
Most players will not notice dramatic visible changes, but the analysis and reporting behind commands like explain world are now more accurate and robust.
Improved world analysis accuracy
Previously, Memento could sometimes infer that world analysis was complete purely from map counts. On large worlds, discovery could populate the world map before the scanner had actually finished its work.
This could make the world appear fully analyzed earlier than it really was.
Version 0.9.15 introduces a small lifecycle model for world analysis. Memento now distinguishes between:
- discovering the world
- scanning the world
- completing the analysis
A world is now only considered fully analyzed once scanning has actually finished.
This makes status reporting more accurate and avoids edge cases on larger worlds.
Command improvements
The following commands now use the improved lifecycle evaluation:
explain worlddo scando csv
They now rely on the real analysis readiness instead of inferring completion from counts alone.
New regression test suite
This release also introduces the first deterministic regression tests protecting the world analysis logic.
These tests ensure that:
- a world cannot appear complete before scanning finishes
- mismatched totals are never treated as complete
- lifecycle evaluation remains correct over time
This strengthens the internal safety net as Memento continues to evolve.
Summary
0.9.15 focuses on correctness and long-term reliability:
- more accurate world analysis reporting
- improved behavior on large worlds
- new automated regression tests protecting the logic
As always, feedback is welcome. If something behaves unexpectedly, feel free to open an issue on GitHub or leave a comment on Modrinth.
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:8yUgaMwi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtOQCXON:8yUgaMwi"
}

