Minecraft /give command
The /give command hands a player an item straight from the console or a command block, no crafting or creative inventory needed. The part that trips people up is that the extra item data changed format across versions: writing the wrong syntax for the server you run makes the command fail silently or throw a parsing error.
Each property is a separate component inside the brackets, and the custom name must arrive as a valid JSON text component wrapped in outer single quotes.
The `Enchantments` tag uses `lvl` instead of a direct value, and the unbreakable flag becomes `Unbreakable:1b`, a byte, not a boolean.
With no enchantments, name or flag, the builder never opens brackets: the command is just item and count, the most common /give use case.
In the 1.20.5 update, Minecraft replaced the NBT system with item components. Commands written in the old format (curly braces) do not work on 1.20.5+, and vice versa. That is why the tool generates both, pick based on your world or server version so the command works first try.
The most common cause is mixing formats: pasting square-bracket `[]` components on a server that still expects curly-brace `{}` NBT (or the reverse). Check your server version before copying the command and use the tool's format switch to generate the right syntax.
Yes. The compatibility check only exists at the in-game anvil; writing both enchantments directly into the command puts them on the same bow with no block.
64, the default stack cap. Asking for more than an item's real max (a tool, for instance, which stacks only to 1) does not break the command, the game just delivers that count across separate inventory slots.
1.20.5 onward, with the item components rewrite. Versions from 1.13 through 1.20.4 use the legacy curly-brace NBT syntax.
/give @p diamond_sword[minecraft:enchantments={"minecraft:sharpness":5},minecraft:custom_name='{"text":"Excalibur"}',minecraft:unbreakable={}] 1The command is generated locally in the browser; nothing is sent to servers.