Links
Tags
Creators
Details
0.9.3-SNAPSHOT
Compatibility
Changes
Visual Stone Identity
This release introduces the first explicit visual identity for Memento stones and lays the structural foundation for richer, time-driven visual effects.
Stone placement now produces clear, intentional particle effects: an anchor at the stone position and a visible projection on the surrounding chunk surface. This restores and validates visualization behavior within the new event-driven architecture.
Under the hood, v0.9.3 strengthens the model significantly:
- Visualization is now driven by domain events, not ad-hoc triggers.
- Visual effects are managed as lifecycle-aware objects, ready for repetition, fading, and long-lived projections.
- A shared game time tracker decouples domain logic from raw server ticks, improving correctness and testability.
- Command handling has been refined so stones are placed on the targeted block, with clear feedback when placement is invalid.
This release is primarily structural: it makes stone behavior visible, traceable, and extensible, preparing the system for future work on influence areas, topology-aware effects, and long-running visual projections.
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:IKLN9JI3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtOQCXON:IKLN9JI3"
}

