Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated 4 months ago
All versions
1.0.1
Beta
DonutAH - Live Numbers 1.0.18 months ago 35
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Changes
DonutAH 1.0.1 Changelog
New Features
Enchantment-Aware Pricing
- Enchanted items are now tracked as unique listings — a Diamond Sword with Sharpness V is treated as a completely different item from one with Sharpness V + Fire Aspect II, or an unenchanted sword
- Item tooltips now show the price specific to that exact enchant combo instead of a blended average across all variants
- The AH scanner stores all unique enchant combinations found on a page — multiple swords with different enchants are each saved separately
Dashboard Enchantment Support
- Items with multiple enchant variants are grouped under one row with a variant count badge
- Clicking an item opens a modal showing each enchant combo and its own price
- Search now works across enchantment names (e.g. searching "sharpness" finds all items with Sharpness)
/donutah reload Command
- New command to sync the price cache with the server without having to relog
- Usage:
/donutah reload
Bug Fixes
- Fixed tooltip always showing a blended average price regardless of enchantments — it now shows the price for the specific enchant combo on the item you're hovering over
- Fixed the scanner treating all variants of an enchanted item as duplicates of the first one found — each unique enchant combination is now correctly stored as its own entry
Technical
- Enchantments are read from the item's
ENCHANTMENTSdata component (the authoritative Minecraft source) rather than lore text, which was unreliable - Enchantment lists are sorted alphabetically before storage and lookup, ensuring consistent matching regardless of lore display order
- Backend
/api/price/:itemnow accepts an optional?enchants=query parameter for enchant-specific price lookups
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:eqopyDjq:1obOVPui"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eqopyDjq:1obOVPui"
}

