/clear

It removes matching items from a player's inventory. It can also count items without deleting them.

Yes. Running /clear without an item filter removes all matching inventory items from the target player. Review the arguments carefully.

Yes. Specify the registered item ID. For example, minecraft:dirt limits removal to dirt instead of clearing the whole inventory.

Yes. With an amount of zero, it detects matching items and returns their count without removing them.

No. It operates on player inventory items, not placed blocks. World modifications require different commands.

Java Edition uses /clear [targets] [item] [maxCount]. Optional arguments are useful, but omitting them can clear the entire inventory.

It specifies whose inventory should be searched or cleared. Use a player name or an appropriate player selector.

It limits the number of matching items removed. At zero, items are counted without deletion.

The command is not restricted to one item type. A normal removal operation may therefore clear the player's whole inventory.

Yes. @a targets all matching players. Be especially careful when combining it with item removal on a public server.

Run /clear @s minecraft:stone 0. It detects matching stone items without deleting them from the inventory.

Use /clear @s minecraft:dirt 10. If fewer than ten matching items exist, only the available amount is removed.

For example, /clear Steve minecraft:cobblestone removes matching cobblestone from Steve. Verify the target player first.

Run /clear @s minecraft:diamond 0 to count matching diamonds. It does not consume the player's items.

Use /clear @s only when you intend to remove all matching items. Move valuable items somewhere safe before running it.

Modern Java versions use item predicates, allowing supported item properties to be checked with the appropriate syntax.

It can check and remove items, but a reliable transaction needs result verification and protection against repeated execution.

Yes. /execute can establish the execution context. Verify the executor and selected player target before running the command.

Yes. maxCount limits removal. If fewer matching items exist, the command does not create or compensate for missing items.

Yes. The command result reports matching items removed or detected and can be used with suitable /execute store logic.

The inventory may not contain matching items, or the filter may be wrong. Check the selected player and target availability.

You may have omitted the item filter or maxCount. Inspect the complete command before trying again.

Without an explicit target, the console has no player inventory of its own. Specify a player name or a suitable selector.

The identifier may be unknown, or the component predicate syntax may not match your version. Start with a plain item ID.

Their arguments differ, including Bedrock's data-related parameter. Do not copy one edition's syntax directly into the other.

Item and component formats have changed across Java Edition versions. Verify that the current version supports your predicate syntax.

Yes. Item components changed many item-related command arguments. Older NBT examples may require conversion.

Java Edition normally requires permission level 2. Removing other players' items should be restricted to authorized users.

First use the same item filter with maxCount zero. It checks matches without actually deleting inventory items.

The /clear command does not provide an automatic undo. Recovery requires previously prepared mechanisms or saved data.