Minecraft Custom Villager Trades Command

Villager trade commands are hard to debug because item data can appear inside buy, buyB, or sell. Keep one trade simple until it works, then add more recipes.

NBTForge is useful here because the command can sit beside related item presets. Build the sold item first, then paste or recreate that item as the sell stack.

• Use maxUses for permanent shops.
• Use rewardExp:0b when trades should not level the villager.
• Use tags for cleanup, protection, or region logic.

A villager shop usually belongs in a larger command pack. Pair the summon command with a region setup, a title prompt, or a backup clear command for test villagers.

Keep trade costs readable. If a shop needs rare currencies, create the currency item as its own Give preset first.

Treat Minecraft Custom Villager Trades Command as a tested starting point, not just a copied string. After the output works once, save it with a clear Project name, note the target Minecraft version, and keep the preset near related setup commands such as scoreboard, bossbar, loot, or reset lines.

Before publishing the preset to a map, server, or command pack, run it from the copied artifact rather than only from the live workbench. That catches missing dependencies, stale selectors, wrong edition choices, and commands that only worked because local test state already existed.

• Keep the selected Edition and Version with the shared command.
• Test selectors against a harmless command before using damage, kill, clear, or teleport.
• Move long commands into Project or a function-style workflow instead of pasting them into chat.
• Recheck warnings after changing entities, item components, passengers, or datapack resources.