Tags
Creators
Details
0.15.0
Compatibility
Required content
Changes
The crit half of the port, Storm's release countdown, and a scoring change you will notice immediately.
What changed
- Crit readout. When Hypixel reports an Explosive Shot hit, the damage per target is divided by your Blessing of Power — read out of the tab footer — and printed to your own chat. Nothing is sent anywhere and nothing is written to party or private chat; the line is local to your client.
- Storm's release window. Storm's cast lines start a countdown on screen, ending in a
SHOOT NOWwindow. Both tick values are settings rather than constants, for the reason under "What is not verified". - ClearPoints now pay for the secrets you find. A room used to be worth 0.25 for every secret it contains, credited when it cleared — so the number never moved while you were collecting, and a seven-secret room paid 1.75 even if you touched none. Now each secret attributed to you adds 0.25 the moment you find it.
Pipesgoes from a flat 2.50 to 0.75 plus what you actually find.
Scores from before this build are not comparable with scores after it. That is the second time ClearPoints has changed kind, and it is deliberate both times.
Everything new is behind a toggle: crit readout on the chat tab of /sa, storm timer and both its tick values on the HUD tab.
The receiver needs nothing
Report schema is unchanged at 6. Sighte/skyblock-server master is 1a7f435, deployed since 2026-08-16. ClearPoints have never left the client, so the scoring change is invisible to the server.
Requirements
Minecraft 26.1.2 · Fabric Loader ≥ 0.19.3 · Java ≥ 25 · Fabric API · fabric-language-kotlin ≥ 1.13.13
sha256 of the attached jar:
5e1987d83823f14d952b5f15613aa77fad21aa383a98db1e0157b3ec32c2bda3
What is not verified
The development client cannot reach Hypixel. Everything below is stated because a played floor is the only thing that settles it:
- Every Hypixel string in the crit readout and the storm timer is a hypothesis. They come from the mod this was ported from, and twenty real session logs on disk contain none of them — no build ever looked. Both features log a debug event when they see something close and fail to match it, so one M7 settles it either way. If Storm speaks and you see neither the countdown nor a
storm_unparsedevent, the line never reached the mod at all, and correcting the wording would not fix that. - The countdown's 138 ticks and its 20-tick window are inherited numbers with no derivation. Unlike a wrong string they will never announce themselves — the timer will count down, turn red and fire, simply at the wrong moment. That is exactly why both are adjustable in
/sarather than compiled in. Correct them once you have watched a real cast. - The 2.5 added per Blessing of Time in the crit calculation is inherited the same way, and produces a plausible number whether or not it is right.
- Which secrets count as yours is still the weak part. A secret you walk over counts as somebody else's, so both the readout and the new points under-credit you. That is a known open item, not a defect in this build.
286 tests, 21 classes, green.
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:XuCA5Jje:YNlbBvlI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XuCA5Jje:YNlbBvlI"
}

