Tags
Creators
Details
0.11.0
Compatibility
Required content
Changes
A new weighting no longer needs a new jar, and a report finally knows which floor it was.
What changed
-
#43
scores-fetch-001— the mod fetches room scores from the receiver at startup instead of using the values compiled into the jar. Resolution is fetched → cached → compiled seeds: no network, a dead host, a 503, a truncated body or an HTML error page all fall back to the last cache and then to the seeds, and none of it delays the game starting. A document that arrives after a run has begun is cached but not adopted, so a weight cannot move mid-run.This is the point of the release. The receiver has measured clear times for 53 rooms now, so the scores it serves already differ from the ones compiled in — and every later improvement reaches you without another download.
-
#45
floorloss-001— a run report carries the floor it was played on instead of?. One line was doing two jobs: the assignment that recorded the floor was the in-dungeon check, so every check made outside a dungeon erased it, and the report is written after leaving. Measured before the fix: 20 of 22 uploaded reports carried?.
What this changes for older installs
Nothing breaks. A 0.10.0 client keeps uploading successfully; its reports simply keep carrying ?
for the floor and it keeps scoring rooms from the values in its own jar.
Reports already uploaded are not repaired — profiles/ is permanent and append-only, so the floor of
past runs stays unknown.
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 a11add5140e414f209134e37454ad717551a8745adf9171990be74482eec4bdf
What is not verified
The development client cannot reach Hypixel, so the following are reasoned from source rather than seen in a real dungeon — unchanged from 0.10.0 except where noted:
- That a real report now carries its floor end to end. The remember/forget/answer decision is tested
on real sidebar strings and five mutations are caught, including the plausible wrong fix; what is
untested is that
reset()lands on the JOIN edge of every real run. runloss-001's DISCONNECT trigger, still read out of the call graph rather than observed.chat-001's line patterns, cited from published mods and checked against their sources, but never seen coming from Hypixel — and whether a chat secret line arrives before the action-bar update it attributes is still open.- Party attribution. The decoration-order heuristic has never run against a real party.
- One boundary recorded rather than fixed: the receiver validates
flooragainst?|E|[FM][1-7], and the mod's floor string could in principle beEntrance, which would be rejected. Measured as unreachable today.
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:iLTiCxp1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XuCA5Jje:iLTiCxp1"
}

