Most of these need operator permission — run them from an op's chat, a command block, or the server console.

How to Use the Recipe Command Generator

  1. Pick a mode: Give to unlock a recipe (so it shows in the crafting book and can be crafted), or Take to lock it again.
  2. Enter the Target player – the default @s targets the command’s executor.
  3. Enter a Recipe ID such as minecraft:diamond_pickaxe, or use * to affect every recipe in the game at once.
  4. Copy the generated /recipe command into a command block, the console, or an operator’s chat.

Command Syntax Reference

/recipe give <target> <recipe>
/recipe take <target> <recipe>

/recipe controls recipe knowledge, not inventory contents – it decides whether a recipe appears highlighted in the crafting/furnace/smithing recipe book and whether shapeless/shaped crafting is allowed to complete for that recipe when the doLimitedCrafting gamerule is enabled. The recipe ID always matches the item it produces, using its namespaced ID like minecraft:diamond_pickaxe or minecraft:golden_apple. Using * in place of a specific ID applies the action to literally every recipe registered in the game, which is the fast way to unlock (or lock) the entire recipe book at once.

Frequently Asked Questions

Does /recipe give actually put the crafted item in my inventory?

No – /recipe give only unlocks the recipe’s knowledge/crafting-book entry, it does not give you the item itself or any ingredients. To actually receive the item, you still need to craft it (or use a separate /give command).

What does /recipe take actually prevent?

By default, in normal survival, recipe knowledge mostly affects the crafting book highlight – most players can craft anything they have ingredients for regardless of “known” recipes. /recipe take becomes a hard restriction specifically when the doLimitedCrafting gamerule is turned on, at which point only known/unlocked recipes can actually be crafted.

What recipe ID do I use – the recipe’s name or the item it produces?

Recipe IDs match the item produced, using its namespaced ID, such as minecraft:iron_ingot for smelting iron or minecraft:shield for crafting a shield. A few special recipes (like different banner pattern combinations) have their own distinct IDs separate from a plain item name.

Does using * unlock recipes that are normally hidden until an advancement is earned?

Yes – /recipe give <target> * force-unlocks every recipe in the game immediately, bypassing the advancement triggers that would normally reveal them gradually through natural play.

Related Tools