Links
Tags
Creators
Details
0.9.4-SNAPSHOT
Compatibility
Changes
Changes in this release
This release is focused on in-game visualization of stone influence.
Stones now visibly project their presence into the world, making it easier to understand where, when, and why areas are affected — without requiring any client-side mods.
In-game visualization
-
Stones now show surface-level visual effects:
- when a stone is placed
- when an area enters a waiting state
- when an operator explicitly visualizes stone influence
-
Visual effects project onto the terrain surface and into the air, making affected areas readable at a glance
-
Anchor effects clearly mark the exact location of stones, even from a distance
New visualization command
-
Added
/memento visualize- Explicitly displays a stone’s area of influence
- Useful for inspection, demonstrations, and explaining behavior to other players
Improved command semantics
-
Renamed
/memento setto/memento alter- Better reflects that existing stones are being modified
- Behavior remains unchanged
New server-side effects system
-
Introduced a brand-new visual effects pipeline
- Built entirely on vanilla particle effects
- Fully server-side — no client mod required
-
Effects are driven by game time, not ticks
- Short-lived effects (placement, visualization)
- Long-lived ambient effects (waiting areas)
Foundation for future work
- The new effects system is intentionally flexible and extensible
- Provides a stable base for future visualizations without increasing client complexity
- Internal structure has been simplified and cleaned up to support further iteration
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:o95mpmMc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtOQCXON:o95mpmMc"
}

