Tags
Creators
Details
Licensed MIT
Published 10 months ago
Updated 3 weeks ago
All versions
1.21.1-1.2.0
Release
betterpiglintrades 1.21.1-1.2.02 months ago 135
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Better Piglin Trades 1.2.0
A correctness release for Minecraft 1.21.1. If you are on 1.0.0, this is a recommended update.
Fixed
- Clients without JEI were disconnected on login. The trade sync handler reached into the JEI integration unconditionally, so any client without JEI installed hit a missing class while handling the join packet. This is the main reason to update
- JEI showed no piglin bartering recipes when connected to a dedicated server. Recipes are now built from the synced output data instead of the server-side trade definitions
- Trade data was not re-sent to connected players after
/reload, leaving JEI showing stale rewards - Right-clicking a piglin with a custom trade item produced no arm swing, and could trigger the item's own right-click action, because the client was not told the piglin would accept it
- 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
- Removed an injection into a piglin method that has no callers left in modern Minecraft
Added
enabledfield on trade definitions. Set it to false to take an item out of bartering entirely, rather than only removing its rewards- JEI now shows the chance of each barter output on its tooltip, sorted most likely first
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
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:v5cY5EAR:p7mvUxy8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v5cY5EAR:p7mvUxy8"
}

