Tags
Creators
Details
0.9.0
Compatibility
Required content
Changes
First tagged build. Cut from main at 2c0163d; the jar itself has been unchanged since b6954da,
because everything merged after it is server-side.
Install sighteaddons-0.9.0.jar into mods/. Do not use the jar from dist/ of an older commit
— see Older builds below.
What changed
- The upload endpoint moved to HTTPS (#24). Caddy terminates TLS on the analysis box and forwards to the receiver on loopback; the plain-HTTP port no longer answers from the internet. The public URL is compiled into the jar, which is why this needs a build rather than a config change.
- A dungeon you leave early is now reported too (#23). Until now a run report was written only on
Hypixel's end-of-run headline, so walking out of a floor threw away every room the party had already
cleared — which is most runs. Report schema 4 adds
complete, so a partial run is usable data instead of an indistinguishable one. - The
/safooter no longer promises a key escape does not press (#22). With a type chip active and no search, it saidesc closewhile escape reset the chip and kept the screen open. - Receiver: refusals are logged against the real client rather than the proxy, and
X-Forwarded-Foris read from the right and only if it parses as an address (#25, #26). No jar involvement.
Older builds
0.8.0 and earlier have the plain-HTTP URL compiled in and can no longer reach the box at all. Nothing
of theirs is lost — a failed connection leaves the report in config/sighteaddons/runs/ and it is
retried at every game start — but nothing arrives from them until their owner installs this build.
Requirements
| Minecraft | 26.1.2 |
| Fabric Loader | >= 0.19.3 |
| Java | >= 25 |
| Fabric API | 0.155.2+26.1.2 |
| fabric-language-kotlin | >= 1.13.13 (built against 1.13.13+kotlin.2.4.10) |
Client-side only. sha256 of the attached jar:
e043d1d2a5ff44e39443d2bc065404f0996a521290272095254147fafcf02135
Verified, and not
Green: 79 Kotlin tests, 124 Python tests. The TLS endpoint was checked end to end before the URL was
changed — valid Let's Encrypt chain, /health 200, Caddy forwarding /runs and /ingest, and the
old port refusing connections. An abandoned-run report was validated through check_run, to_store
and roomstats.fold on the exact shape the mod writes.
Not verified in a real dungeon, because the dev client cannot reach Hypixel: an upload actually
landing over TLS from in-game, a complete: false report arriving server-side, the escape order in
the /sa history by hand, and RunReport.restampPending(), which has still never executed.
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:Ja2UObhF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XuCA5Jje:Ja2UObhF"
}

