Skip to content

Minecraft /give Command Generator

Build a /give command with a custom name, lore, enchantments and an unbreakable flag, then copy it straight into your server console. Pick the version your server runs and the generator writes the syntax that version actually accepts.

Current syntax. Data components, with the enchantment list written flat: enchantments={sharpness:5}.

Name and lore

Enchantments

Limited to what swords accept

Your command

/give @p netherite_sword

Targets 1.21.5 – 26.2 on Java Edition. Drop the leading slash when you paste it into the server console — the console does not take one.

Getting /give to behave

Most "the command doesn't work" reports come down to one of these, and none of them produce a useful error message.

  1. 1

    The item syntax changed twice, and old generators never caught up

    Minecraft 1.20.5 replaced item NBT tags with data components, so {Enchantments:[{id:"minecraft:sharpness",lvl:5}]} became [enchantments={levels:{sharpness:5}}]. Then 1.21.5 flattened that again to [enchantments={sharpness:5}]. A command copied from a 2023 video is not slightly wrong on a current server — it fails to parse outright. Set the version above before you copy.

  2. 2

    Bedrock cannot do this at all

    Bedrock's /give takes a components argument, but it only accepts can_place_on, can_destroy, item_lock and keep_on_death. There is no Bedrock /give that puts a name, lore or an enchantment on an item, so anything claiming otherwise is generating a command your server will reject. On Bedrock, enchant the item in hand with /enchant instead.

  3. 3

    Custom names are italic unless you say otherwise

    Minecraft renders any custom-named item in italics, which is why renamed gear looks subtly wrong next to vanilla items. Writing italic:false into the name component is the fix, and it is on by default here.

  4. 4

    The console does not want the leading slash

    Typed in chat, commands start with /. Run from the server console or through RCON, that slash is part of the command name and the parser rejects it. Same command, one character of difference, and the error says nothing useful.

  5. 5

    /give ignores the rules an anvil enforces

    You can hand someone Sharpness 255 on a fishing rod with /give, because the component is written straight onto the item. /enchant will not: the wiki notes it enforces maximum levels and compatibility. That is a feature when you want a joke item and a trap when you wanted a legitimate one, so this tool holds you to the real limits by default.

  6. 6

    One command can only carry 100 stacks

    Since 1.17, /give caps at 100 stacks worth of items in a single command — 6,400 of something that stacks to 64, but only 100 of a sword or any other unstackable item. Ask for more and the command fails rather than giving you what it can.

A console you can actually reach.

Every plan comes with a live console and RCON, so running commands does not mean waiting on a support ticket — plus NVMe storage, automatic backups and DDoS protection.