Links
Tags
Creators
Details
All versions
1.21.1-2.1.1
Release
Trade Tweaks 1.21.1-2.1.1last week 94
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
2.1.1 CHANGELOG
NEW
- Added a dedicated Trade Tweaks advancement tab with 17 advancements covering all Emerald Wand modes, trade selection, consumable villager tools, and trade broadcasts.
- Added a live JEI-style replacement search field to the trade selection screen, including prefix filters, combined/excluded terms, and keyboard-focused text editing.
- The custom trade selection lists have been replaced with a two-column interface using the vanilla villager trading visuals and controls
FIX
- Trade replacement candidates are now generated from the server's fully loaded trade tables, adding generic support for modded villager professions and data-driven trades.
- Randomized category-based trade factories now expose every distinct item variant they can generate instead of showing only one random example, covering modded groups such as logs and signs without profession-specific rules.
- Candidate generation now uses the real villager context without consuming the villager's random sequence.
- Trade levels are resolved from the villager's actual career unlock order. Both trade slots unlocked at the same level now share the same candidate pool.
- Trade replacement now uses short-lived server sessions and validates the selected candidate, villager, distance, wand, and original offer before applying a change.
- The trade selection screen no longer pauses single-player worlds, preventing the emerald wand's nearly finished cooldown overlay from flickering.
- The trade selection screen now closes if its villager dies, unloads, or moves more than 8 blocks away.
- Opening the trade selection screen now occupies the villager through its vanilla trading state, preventing it from wandering until the session ends.
- Vanilla trading and trade selection now lock the villager for other players. Conflicting trade selection, upgrade, profession reset, and restock actions are rejected.
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:P5pFKnk6:J3DTivsI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:P5pFKnk6:J3DTivsI"
}

