Tags
Creators
Details
1.21.4-2.1.0
Compatibility
Required content
Changes
Website updates:
- Added support for Bedrock players (Geyser/Floodgate) (skins and nicks)
- Some fixes when DB is not initialized ...
- Fixed error in HoF page with less than 15 players
- Added description to the HoF page, explaining how points are calculated
- Some minor changes in layouts, colors, visual bugs, ...
- Added new page with individual stats (available by clicking on any statistic)
- Optimized DB loading (now caches the database after the first download, so the loading is much faster - the cache is revalidated every hour)
Mod updates:
- Included new updated website
- Added support for non-default stats folder
- Added tag for non-default stats folder (conf bump to 1.0.2) ~ More information below
- Added optimizations (updates only when there are changes)
- Some minor changes and fixes
- Added support for Bedrock players (Geyser/Floodgate)
- Fixed issue with syncing stats (players not being updated after first sync)
How to update from version 2.0.3:
- Delete the old mod and upload the new one
- (not required) Delete the old config and have a new one generated or...
- You can manually modify the config to the new version, just change the version inside config to
1.0.2and add the sectionstats-folder = ""to the root. (The changes and how the new config should look like can be seen at this link).
More info:
If there is any problem with the data on the site, it is possible to force an update using F12 (or right click on website and open Developer Tools), then Application, select IndexDB > PlayerStatisticsDB in the list and click Delete database. Then when you reload or open the site, the database will be reloaded.
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:sdjBlHDz:md0B2GgC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sdjBlHDz:md0B2GgC"
}

