Villager Trade
by Pankraz01
Villager Trade lets server owners spawn custom villagers that offer trade options defined by the owner, with recipes that take up to three inputs per row.
What it does
Custom villagers spawned with Villager Trade keep their trade offers and remain in place once placed. Trades are set through a custom trade screen with a themed layout, and each row can take up to three input items. Default settings make the spawned villagers invulnerable and frozen, and both behaviours can be toggled through the villager settings. Trade data persists across dimensions, so a villager keeps its offers when a player travels to another world.
The mod is installed on the client and on the server, since both sides need it to show the custom villagers and their trade screen. It requires Architectury API on both loaders. Files are published for Fabric and NeoForge across 11 release versions, 1.21.1 – 1.21.11, and the code is open source under the MIT License.
The command that manages villager trades is named villager tradings.command.villager. On Fabric it uses the Permissions API v0 and v1 when present, and otherwise falls back to operator level 3. Build artifacts for each loader are produced under the subproject build/libs with the villager tradings prefix.
Key features
Custom villager spawning
Owners can spawn villagers that carry their own trade options, and the spawned villagers persist in the world.
Multi-input trades
Each trade row accepts up to three input items, so recipes can combine several items into one offer.
Themed trade screen
A custom trade screen lays out the offers and inputs in a themed interface.
Invulnerable and frozen defaults
Spawned villagers are invulnerable and frozen by default, and both settings can be changed in the villager settings.
Compatibility
Latest build for each game version and loader.
1.21.x11 of 11 versions with builds
Only full game releases are shown. This mod publishes no snapshot builds.
Requirements
Dependencies declared by the latest file for each loader.
Required 1
Use cases
Who it’s for: Server owners and map makers who want villagers with custom trade lists and multi-input recipes. Players on a server that runs the mod need it installed as well.
How it compares
Better Villager Trading is client-side only and open source under the MIT License, with files for 1.21.1. Visible Traders runs on client and server under the MIT License and is open source, with files for 1.20 – 26.3. Bulk Villager Trading Reborn is client-side only and not open source, with files for 1.21.1. Villager Trade differs from all three in covering 1.21.1 – 1.21.11 on Fabric and NeoForge.
| Mod | Loaders | Game versions | Environment | Updated |
|---|---|---|---|---|
| Villager Trade | Fabric and NeoForge | 1.21.1 – 1.21.11 | Client and server | 2025-12-15 |
| Better Villager Trading | Fabric and NeoForge | 1.21.1 | Client-side only | 2025-07-20 |
| Visible Traders | Fabric and NeoForge | 1.20 – 26.3 | Client and server | 2026-07-11 |
| Bulk Villager Trading Reborn | Fabric and NeoForge | 1.21.1 | Client-side only | 2026-07-29 |
Questions
Does Villager Trade require Architectury API?
Which loaders does Villager Trade support?
Does a server owner need to install the mod on the client?
More from Pankraz01
What the author says
Custom trading villagers with configurable multi-item recipes for Fabric and NeoForge. Permission: villager_tradings.command.villager (Fabric Permissions API v0/v1 if present), otherwise OP level 3.
Official listing
- Modrinth page
- modrinth.com/mod/villager-trade
- Owner
- Pankraz01
- Published
- 2025-12-14
- Updated on Modrinth
- 2025-12-15
- Facts verified
- 2026-10-15