Tags
Creators
Details
All versions
1.1.0+26.2
Release
Release 1.1.0 for Minecraft 26.22 months ago 439
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platforms
Fabric
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Changes
Added
- Bundled vanilla 26.2 trade snapshot inside the JAR (
assets/tradechoice/fallback/vanilla_trades_26.2.json) — covers all 13 villager professions across 5 levels + 3 wandering-trader profiles (68 trade sets) and the 40 enchantments in vanilla'stradeableenchantment tag, each annotated withmax_level. - New
VanillaTradeSnapshotloader (lazy singleton, double-checked locking) for accessing the bundled snapshot data via the classpath resource. - Three-tier fallback resolution in
TradeWishlistScreen.buildEntries(): canonical TRADE_SET registry lookup → bundled vanilla snapshot → liveMerchantMenuoffers as last resort.
Fixed
- Multiplayer crash on dedicated servers that don't sync the TRADE_SET dynamic registry to clients (e.g.,
non-vanilla dedicated server). The Wanted trade panel previously threwIllegalStateException: Missing registry: ResourceKey[minecraft:root / minecraft:trade_set]on non-vanilla servers; it now degrades gracefully through the bundled snapshot. - Tier-3
MerchantMenufallback deduplication: multiple live offers of the same enchantment at different levels (e.g., Efficiency I / II / III) no longer render as duplicate wishlist rows — enchant levels collapse to0forWantedTradeequality, matching the canonical and snapshot paths. - Tier-3
MerchantMenufallback enchantment picker:entryMaxLevelsnow look up the enchantment's real maximum level from the bundled snapshot instead of being hardcoded to1, so the level picker on enchantment rows renders the correct range.
Optional dependencies
Any compatible version
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:jqSyrAQy:G0chgpfc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jqSyrAQy:G0chgpfc"
}

