Tags
Creators
Details
1.20.1-1.2.0
Compatibility
Changes
Better Piglin Trades 1.2.0
First CurseForge and Modrinth release for Minecraft 1.20.1, on Forge.
Data-driven piglin bartering: define which items piglins accept and what they give back, using datapack JSON. Ships with tiered gold nugget, gold ingot and gold block trades.
Features
- Add, override or disable barter items with datapack JSON, no code required
priorityfield to override trades from other packsenabledfield to take an item out of bartering entirely- JEI integration showing every possible reward sorted by chance, with the per-roll chance on each tooltip. Outputs are synced from server to client, so it works in singleplayer and on servers
Fixed since the 1.20.1 maven build
- The mod's own default trades never loaded. The jar had no
pack.mcmeta, so Forge rejected its built-in datapack and none of the gold nugget, ingot or block trades registered - A cached build could ship without the mixin refmap. The refmap is produced as a side effect of compilation and was not a declared task output, so a Gradle build-cache hit silently dropped it, leaving every mixin injection unable to resolve at runtime
- Clients without JEI were disconnected on login
- JEI showed no recipes when connected to a dedicated server
- Trade data was not re-sent after
/reload - Right-clicking a piglin with a custom trade item gave no arm swing and could trigger the item's own right-click action
- Custom trade items were consumed in creative mode
- Barter rewards dropped at the piglin's feet instead of being thrown toward the player
- Piglin repellents could be picked up as trade items
Notes
- Trade overrides should live in your own namespace and use a higher
priority. Writing todata/betterpiglintrades/piglin_trades/<name>.jsonis unreliable, since only one pack can win a given file path - Loot tables go in
data/<namespace>/loot_tables/on 1.20.1
Optional dependencies
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:v5cY5EAR:5Cg5F4DU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v5cY5EAR:5Cg5F4DU"
}

