My command does not work
The game usually tells you what is wrong — just in terse English that reads like it said nothing. This page translates the messages you actually hit and names the usual cause of each
Check these three first
Most problems end here, before you start reading the syntax character by character
- Are cheats on? — If not, nearly every command is unavailable How to enable them
- Is it the right edition? — A command from a Java guide usually will not run on Bedrock as-is, and vice versa
- Is it the right version? — Item syntax has changed twice, so an old video’s command can fail even on the same edition Read more
What the game’s message means
| Message | Means | Usually caused by |
|---|---|---|
Unknown or incomplete command |
The command is unknown, or it is unfinished | A misspelled command name, or one that does not exist on this edition |
Expected whitespace to end one argument |
The argument should have ended here but more characters followed | A missing space, or one bracket or quote too many |
Incorrect argument for command |
The value is of the wrong kind | Text where a number was expected, or an item id that does not exist |
No entity was found |
Nothing matched the selector | The bracket filter is too narrow, or no such mob is nearby |
You do not have permission to use this command |
You are not allowed to run it | Cheats are off, or you are not an operator on this server |
That position is not loaded |
That area of the world is not loaded | The coordinates are too far from every player |
It runs, but nothing happens
This case is harder because the game says nothing at all. The syntax was fine — it just ran against nobody, or in the wrong place
| Likely reason | How to confirm it |
|---|---|
| The selector matched nobody | Temporarily swap the command for a say using the same target — silence means the target does not exist |
| The position anchor is wrong | Replace ~ with absolute numbers — if that works, the anchor was the problem |
| The command block never fired | Put a test say in the block first — no message means the block setup is the issue, not the command |
| An if condition did not hold | Strip the if off temporarily — if it then runs, the condition was the blocker |
A systematic way to narrow it down
Rather than staring at one long line, cut it down piece by piece until you have the shortest version that still fails. This finds the cause far faster
- Start with the shortest possible form, e.g. /give @s minecraft:stone 1 — if even that fails, the advanced options are not the problem
- Add the removed parts back one at a time, running it after each
- Whichever part breaks it on being added back is the culprit
- Rebuild that part with our tool and compare it against what you typed
In Java’s chat the command is coloured as you type, and the part that turns red is where the game stopped understanding it — you can locate the fault without pressing Enter
Still stuck
If a command our tool built does not work in game, that is our bug, not yours. Report it with the edition and version you are on and we can track it down
Other guides to read next
- Minecraft command basics — Start from zero: how to enable cheats, where commands can be typed, and enough about selectors and coordinates to get going
- Target selectors in depth — A deep look at the square-bracket arguments, from type and distance through limit and sort, plus how to work out why a command matched nobody
- Coordinates: numbers, ~, and ^ — Why ~ and ^ cannot be mixed, why blocks end up in the wrong place, and which form to reach for in which situation
- Command blocks — Take the commands you generated and run them automatically — once, on repeat, or chained one after another
- Why an old give command stops working — Legacy NBT, 1.20.5 components, and 1.21.5 components side by side — compared using commands built by the generator itself
- Scoreboard basics — Create an objective the game tracks for you — or track it yourself from a command block — then use the score as a condition elsewhere
- The execute command — The most powerful command in the game, taken apart piece by piece — how as differs from at, and why reordering changes the result