Tags
Creators
Details
2.8.1+mc1.21.11
Compatibility
Required content
Changes
Lifetime Stat Tracker 2.8.1
Shared Tempest Studios data folder with player-profile storage and
instance-aware local worlds for Minecraft 1.20 through 26.2-pre-3.
Choose the file that matches your Minecraft range:
1.20-1.20.41.20.5-1.21.101.21.1126.1-26.2-pre-3
Highlights:
- Lifetime Stat Tracker now writes saved JSON data under the shared Tempest
Studios app-data folder:
- Windows:
%APPDATA%\TempestStudios\Lifetime-Stat-Tracker\ - macOS:
~/Library/Application Support/TempestStudios/Lifetime-Stat-Tracker/ - Linux:
$XDG_DATA_HOME/tempest-studios/lifetime-stat-tracker/or~/.local/share/tempest-studios/lifetime-stat-tracker/
- Windows:
- Actual JSON files live under
profiles/<player profile>/inside the shared root, so one Minecraft account keeps one running total across launchers and instances. - Singleplayer world handles now include the active game directory namespace, so
two different instances with a world named
worlddo not collide inside that shared player-profile total. - On first run, existing unnamespaced data is copied into the active
player-profile folder if that folder does not already contain tracker data.
The migration checks unnamespaced shared-folder data first, then any
instance-scoped
2.8.1pre-release test data, then2.8.0app-data, then older launcher-local.minecraft/config/lifetime-stat-tracker/data. - Each legacy source is auto-imported only once to avoid copying a mixed old dataset into every future player profile.
- Legacy data is left untouched as a safety backup.
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:rJCvFZKh:qviT48uq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rJCvFZKh:qviT48uq"
}

