Tags
Creators
Details
0.12.0
Compatibility
Required content
Changes
A room record is now only written when the work was yours.
What changed
-
#48
recordowner-001— walking into a room somebody else is already working no longer writes a personal best for you.- A secret run counts only if every secret in that room was attributed to you, and the mod saw
the room from its true start — it had read the secret counter at
0when you walked in. - A room clear counts only if you were in the room from the moment its clock started and spent more time in it than anybody else. Both, not either.
Before this build, one second in a room was enough for a clear, and a room where a teammate did the work still credited you. A clear that landed as you arrived wrote a ~1.5 second time that then beat every honest record for that room, permanently.
The chat lines themselves are unchanged: the clear line still names whoever actually cleared the room, and the secret line still carries
(N, M yours). One narrowing — with own PBs only switched on, a run the new rule refuses no longer prints at all. - A secret run counts only if every secret in that room was attributed to you, and the mod saw
the room from its true start — it had read the secret counter at
Far fewer records will be written, and solo floors are hit just as hard
This is the part to read before wondering whether the mod has stopped working.
The one real dungeon floor committed to this repository as evidence —
docs/evidence/session-1786719912927/, a solo, deathless M7 — has five completed secret runs.
Under the new rule four of the five no longer record:
| Room | Secrets | Counted as yours | Recorded now |
|---|---|---|---|
| Atlas | 6 | 4 | no |
| New Trap | 3 | 2 | no |
| Slime | 5 | 2 | no |
| Chains | 2 | 2 | yes |
| Pipes | 7 | 5 | no |
Every secret on that floor was yours — nobody else was there. So what fails is not the rule, it is the mod's ability to recognise your own finds. A secret is credited to you only if you right-clicked a chest, lever or secret skull within about two seconds of it counting, or Hypixel named you in a wither-essence chat line. A secret picked up by walking over it counts as somebody else's and sinks that whole room's run.
That gap is tracked as ownsecrets-001 and is not fixed in this build. If your personal bests stop
appearing, this is why — it is a known, measured limitation and not a mistake in your play.
What this changes for older installs
Nothing breaks. The upload URL and the report schema are unchanged, so 0.11.0 and earlier keep reporting normally and keep writing records under the old rule.
Records already in history.jsonl are not repaired. Rooms whose best time was set under the old,
wrong rule keep that time, so a genuinely earned record may simply never beat it. Nothing is rewritten,
reinterpreted or migrated — this was a deliberate choice, not an oversight.
Requirements
| Minecraft | 26.1.2 |
| Fabric Loader | ≥ 0.19.3 |
| Fabric API | 0.155.2+26.1.2 |
| fabric-language-kotlin | ≥ 1.13.13+kotlin.2.4.10 |
| Java | ≥ 25 |
sha256 378bec73a535c22ce52bfb5449ec0803242d5b773f1001c55af57c98e0f08c0b
What is not verified
The development client cannot log in to Hypixel, so nothing that needs a real dungeon has been seen running. For this release that means two specific things, named rather than left to assumption.
-
Neither gate has ever run in a game. The decisions themselves are unit-tested and swept with 21 deliberate mutations, but the four lines that call them need a live client — and two of those probes (S and T) exist precisely to measure that nothing in the test suite guards those four lines. They come back uncaught every run, by design, as a standing reminder of exactly this.
-
The secret-run gate now depends on the mod having read a trusted
0/Nsecret counter on entering the room. This is the sharp one. If Hypixel does not deliver a0/Nbar for a room the mod has already identified, secret records do not become rare — they stop entirely.Hypixel is known to send a
0/Nbar:session-1786567867893.jsonlline 85,t=137, carriesbarFound: 0for the Slime room. But it arrived on a room whose bar reported 7 secrets where the database expected 5, so the mod logged it as a mismatch and the trusted path remains unproven.One played floor settles this. The build writes
secret_room_first_barwhen it takes a trusted first reading, andfirstBaron everysecret_run_discarded, intoconfig/sighteaddons/debug/session-<millis>.jsonl. Ifsecret_room_first_barnever appears, or always carriesuntouched: falsefor rooms you walked into clean, the gate has closed the door on every record rather than on the wrong ones.
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:diMDvw5I"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XuCA5Jje:diMDvw5I"
}

