Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 3 weeks ago
All versions
1.0.11+26.1.2
Release
Dungeon Run tracker 1.0.11+26.1.23 weeks ago 436
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
DRT 1.0.11
Kuudra fixes and other fixes
Kuudra
- Key costs are now read directly from the Mage Shop and Barbarian Shop for Basic through Infernal
- Key prices include your own discounts like emissary reputation and Seal of the Family
- Tiers you haven't seen in the shop yet still use the old reputation-based estimate
- Your Kuudra pet perk now increases Crimson Essence value
- Added a new Essence shards +N% setting for extra Crimson Essence value (
/drt config) - Essence amounts with commas like 2,500 now parse properly
- Basic Kuudra chests are no longer counted as Hot
- Plain Kuudra reward chat lines without a header are now read as loot
- Free chests containing only Crimson Essence no longer trigger a false flag
Chest tracking fixes
- Chests that fail to open are no longer logged
- Open cost is recorded correctly again instead of being saved as 0
- If the price feed briefly misses bazaar or auction data, the previous prices are kept instead of items dropping to 0 value
- Normal storage like island chests, ender chests, backpacks and minions no longer shows the reward chest overlay or gets read as loot
Loot history
- Value, cost and profit in the loot list now use current prices and current key costs instead of the values saved when the chest was opened
- Added
/drt debug repriceto update the saved values of old chest records - You can also use
reprice <chest number>to reprice a single chest
Update notice
- DRT now checks for updates when you join
- The update message can tell you if DRT or BetterPV is outdated
- Added a
[Get new update]button - The message also includes a
Join the discord!link
Other changes
- Version bumped to 1.0.11
- Builds are now only made for 26.1.2 and 26.2
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:ZqBAVrEN:qs9BmjOn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZqBAVrEN:qs9BmjOn"
}

