All versions
1.7.1+1.20.4
Release
HikariScoreBoard 1.7.1 (MC 1.20.3 - 1.20.4)yesterday 2
Compatibility
Minecraft: Java Edition
1.20.3–1.20.4
Platform
Fabric
Supported environments
Dedicated servers only
Required content
Changes
First public release since v1.4.6. This is a large jump — please read the breaking change below.
Breaking change
- Inter-server score aggregation has been removed entirely, along with the bundled Velocity
plugin and the
/hikari aggregatecommand. If you used it, those features are gone. Existingsync.jsonandaggregate/files in your world are simply never read again; nothing is deleted. Remove anyvelocity-pluginjar from your proxy by hand. It was removed because nobody used it and it was the mod's only unauthenticated network entry point.
Multi-version support
- Now supports Minecraft 1.17.1 through 1.21.11 (previously 1.18.2 only), across 13 builds. Pick the jar matching your server version.
Performance
- Rankings are now served from a resident in-memory index instead of re-reading every
world/statsfile on each update. Steady-state file reads are eliminated. - Updates are now event-driven: scores appear within one tick (~50 ms) of mining, placing, killing or crafting, rather than on a polling interval.
- The server-wide packet budget that throttled updates when many players were online is gone.
With Hikari-Tweaks installed
- New delta protocol: only changed rows are sent (~30 bytes) instead of the whole list (~6 KB).
- Score values animate smoothly on the client.
- Requires Hikari-Tweaks v1.2.2 or newer.
Vanilla clients
- Fully supported. Clients without Hikari-Tweaks get the ranking in the vanilla sidebar, detected per player, so both kinds of client can be on the same server at once.
Other
/hikarimenu: search block and item rankings by Minecraft ID, and the cursor no longer jumps to the centre of the screen when changing pages.- New
/hikari debugdiagnostic command (OP2). /hikari toplimitnow accepts 1–14.
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:3yeZRJ65:MSdvgfrU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3yeZRJ65:MSdvgfrU"
}

