1.0.0
Compatibility
Required content
Changes
v1.0.0
First public release. Built for 1.21.1 — there wasn't a proper run analytics tool for this version beyond a basic timer.
⌁ Automatic split tracking via advancements — Nether entry caught by dimension change, Bastion / Fortress / Stronghold by advancement completion, dragon kill closes and saves the run
⌁ Analysis tab — not tips from a wiki, it reads patterns from your own runs and points at the specific stage where things fall apart
⌁ Seeds resolved through the integrated server in singleplayer. Multiplayer seeds stay blank — the client doesn't receive them and I'm not going to fake it
⌁ HUD hides itself when the stats screen is open. Took longer to fix than it should have
▸ Death cause is currently logged as "unknown" — proper cause parsing needs a deeper mixin into the damage system, planned for next version
▸ Analysis gets meaningful after 10+ runs — small datasets produce obvious observations
Bugs and suggestions — issues on GitHub.
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:VOqAOaiw:E1NMg9fF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VOqAOaiw:E1NMg9fF"
}

