All versions
1.9.0
Release
Simple Challenge Roulette 1.9.02 days ago 28
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Added
- Per-item records. The mod now keeps the best time for every target item separately, plus the number of runs on that item. Items with a record get a thin accent bar in the item selection grid, and the hover tooltip shows the record and the run count.
- Run history. The last 50 runs are stored: item, modifiers, time, date and result (win / fail / abandoned). File: challengeroulette-history.json in the game directory.
- "History" tab on the statistics screen, switchable with the two buttons at the top.
- Record line on the victory screen: the per-item record plus a golden "New record!" label when the time was improved.
- "Items with a record" counter in the statistics card.
- New strings localized for all 6 languages: EN, RU, DE, ES, PL, ZH. Fixed
- A failed run no longer counts as a win. Previously a challenge failed by Soulbound, No Second Chances or Time Bomb was recorded as a completion: it increased the completion counter and the best time. Now failures only go to the history and never affect progression or unlocks.
- Re-entering a world with an already completed challenge no longer records the same result twice (deduplication by completion timestamp).
- The "Wins" counter no longer shows 0 on the title screen; the duplicated heading on the History tab is gone. Compatibility
- The old challengeroulette-stats.json (format 2 and 1) is read automatically and upgraded to format 3 on the first save. Per-item records start collecting from this run onward — old times were never stored and cannot be restored.
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:zFvLrGlB:4gMqwxRP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zFvLrGlB:4gMqwxRP"
}

