Tags
Creators
Details
0.13.0
Compatibility
Required content
Changes
The run summary stops overstating what it knows about secrets, and starts saying what it does not.
What changed
- The floor's secret total is now the real one. The summary printed the
secrets this client could prove were yours, labelled simply "secrets" — and
it can only prove one in a room you were standing in when the action bar
moved. Measured on two real party M7 floors: only 5 of 19 cleared rooms ever
produced a reading at all. The line now reads
(19 rooms · 10 of 29 secrets), where the total comes from the tab list and does not care where anybody stood. - Teammates get a number instead of a dash, if you put a Hypixel API key in
config.jsonunderhypixelKey. Two snapshots of each party member's lifetime secret achievement, at the start of the run and at the end; the rise is their count for the run. A line below the summary:secrets (Hypixel) Ann 14, Bo 9, You 6 (counted 4). Without a key nothing happens and the summary reads exactly as it did before. (counted N)next to your own name is the gap between what the mod could attribute and what you actually found. It is printed rather than hidden because it is the honest size of a known weakness.
Nothing here changes a personal record, a report field, or what is uploaded. No teammate's name leaves your machine.
Requirements
- Minecraft 26.1.2
- Fabric Loader ≥ 0.19.3
- Fabric API 0.155.2+26.1.2
- Fabric Language Kotlin ≥ 1.13.13 (built against
1.13.13+kotlin.2.4.10) - Java ≥ 25
What breaks for older installs
Nothing. There is no schema change in this build, so an install still on 0.12.0 keeps uploading and keeps being accepted exactly as before.
What is not verified
- No dungeon floor has driven either feature. The development client cannot
log in to Hypixel, so the lines that call this code from the game are covered
by nothing — the logic behind them is, by 35 new tests, but the wiring is not.
If you play a floor,
secret_room_first_bar,secret_api_baselineandsecret_api_settlein the debug log say whether it worked. - The tab-list rows have never been read from a real floor. If Hypixel's format differs from what two other mods document, the total falls back to the old line rather than printing something wrong.
- The Hypixel API itself was checked against the live endpoint: the request shape, the key header and the achievement field all answer as expected, and the rate budget is 300 requests per five minutes against the ten a five-player floor spends.
Checksum
sha256 of sighteaddons-0.13.0.jar:
d6dafa1d81b46a769b62a78ec4428f97a18c849e0429bca1d0d57bd153015bf3
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:wS3OCLGl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XuCA5Jje:wS3OCLGl"
}

