Minecraft commands are slash-prefixed instructions that can move players, alter the world, create items and entities, control time and weather, automate tasks, and administer multiplayer servers. The complete list depends on whether you are playing Java Edition, Bedrock Edition, or Education, your game version, enabled features, and your permissions. The most reliable way to see the commands available right now is to run /help; use /help <command> for that command’s current syntax.
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
What Minecraft commands do
A command is a command name followed by arguments that tell the game what to affect and what result to produce. You can enter commands in chat, place them in command blocks, run saved functions from data packs or behavior packs, or execute them through a supported server console. Most chat commands begin with /; command blocks and functions generally store the command without relying on a chat message.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsCommands can teleport a player, locate a structure or biome, give items, summon mobs, apply effects, build or replace large regions, change game rules, and manage players. They are powerful because the same command can target one entity, every player, or a precisely filtered group.
Enable commands before using them
Bedrock Edition single-player
- Open the world’s settings.
- In Game settings, turn on Allow Cheats.
- Accept the warning and return to the world.
Bedrock permanently disables achievements in that world when cheats are enabled. Turning cheats off later does not restore achievements for that world.
Java Edition single-player
Enable Allow Commands when creating the world. In an existing world, open the pause menu, choose Open to LAN, enable Allow Cheats, and start the LAN world for the current session. World Options also provides the command setting where supported by the current release.
Multiplayer
You need an appropriate operator or permission level. A server owner can grant operator status with /op <playername>, while /deop <playername> removes it. Server permission plugins, realms settings, and command-block permissions can impose additional limits. Never grant operator access casually: it allows world-changing and player-management commands.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Use /help as the live command list
There is no dependable single number for “all Minecraft commands.” Java, Bedrock, and Education expose different commands and argument forms, and releases add, remove, or rename commands. Microsoft’s Bedrock guidance states that running /help by itself lists every command you can run. Use /help <command> to display that command’s usage and available syntaxes.
/help— list commands available in the current world and permission context./help give— show the current/giveforms rather than relying on an old example.- Use the chat autocomplete menu after typing
/or part of a command. It filters names and fills valid arguments, including coordinates and identifiers.
This runtime check is especially important for command blocks, experimental features, server software, and cross-edition tutorials.
Command syntax fundamentals
Names and arguments
A command starts with a name, then arguments separated by spaces. Arguments can identify a target, coordinate, item, entity type, amount, game mode, JSON text, or condition. Angle brackets in documentation mean a required value; square brackets mean an optional value. Do not type the brackets themselves.
For example, current Bedrock syntax is /give <player: target> <itemName: Item> [amount: int] [data: int] [components: json]. The player and item are required; amount, data, and components are optional. /give @s diamond 64 gives the executing player 64 diamonds.
Target selectors
| Selector | Targets | Typical use |
|---|---|---|
@s |
The command executor | Give an item to yourself or affect the entity running a command block |
@p |
Nearest player | Reward the closest player |
@a |
All players | Apply a rule, message, or effect to everyone |
| A player name | One named player | Target a specific online player |
Many selectors also accept filters in the current edition, such as distance, type, scores, or tags. Check autocomplete and /help because selector options and punctuation differ between Java and Bedrock.
Coordinates and execution context
Commands that act at a location accept coordinates. Absolute coordinates use the world’s X, Y, and Z values; relative coordinates use ~ to offset from the executor’s position, which is useful in a command block. Local coordinates using ^ are relative to the executor’s facing direction where supported. A command run from a command block executes at the block’s location unless the command changes its executor or position, commonly with /execute.
Dimensions matter: a coordinate in the Overworld is not automatically the same location in the Nether or the End. If a command fails, verify the dimension, loaded chunks, target type, and whether the destination is inside world limits.
Rank #4
- BUILDING TOY FOR KIDS – The Fox (21588) LEGO Minecraft building toy lets boys and girls ages 10 years old and up recreate a beloved Minecraft character
- POSABLE MINECRAFT FOX – Young builders can assemble the game's classic character with movable legs, a rotatable neck, repositionable head and a reversible eye section, showing the fox with eyes open and closed
- PLAY & DISPLAY – Once playtime is over, the posable fox figure can be positioned awake and standing, sitting with head tilted, or asleep and lying down to create fun Minecraft decor that's sure to delight fans
- ACCESSORIES FOR PRETEND PLAY – Features the fox's favorite snacks: berries and an egg
- GIFT FOR GIRLS & BOYS – Makes a fun birthday gift or anytime present for kids and gaming fans who love Minecraft toys and hands-on creative play
Shared commands and what each one does
The following commands appear in the all-edition portion of the Minecraft command index, but exact arguments and availability can still vary by release. Confirm each syntax with the current world’s help output.
| Command | Purpose | Important notes |
|---|---|---|
/clear |
Remove items from an inventory | Can target a player and, where supported, an item and amount. |
/clone |
Copy blocks from one region to another | Requires source and destination coordinates; large regions can be expensive. |
/damage |
Apply damage to entities | Damage types and optional causes are edition-dependent. |
/deop |
Remove operator status | Requires sufficient server authority. |
/difficulty |
Set or query difficulty | Typical values include peaceful, easy, normal, and hard. |
/effect |
Add or clear status effects | Specify a target, effect identifier, duration, and often amplifier. |
/enchant |
Enchant an item held by a target | The held item and enchantment must be valid for the edition. |
/execute |
Run another command under changed conditions | Can alter executor, position, rotation, dimension, or conditional tests. |
/fill |
Fill a region with a block | Supports modes such as replacing or hollow construction where available. |
/function |
Run a saved function | Packaging differs between Java data packs and Bedrock behavior packs. |
/gamemode |
Change a player’s game mode | Use the edition’s accepted names or numeric forms. |
/gamerule |
Set or query a game rule | Rule names and value types differ by edition. |
/give |
Give items to players | Target, item, amount, data, and components depend on edition. |
/help |
Display command help | Use it as the authoritative list for the current world. |
/kick |
Remove a player from a multiplayer world or server | Requires appropriate authority and may not be available in every context. |
/kill |
Kill selected entities | Without a target, behavior depends on the executor and edition. |
/list |
List online players | Availability depends on the multiplayer environment. |
/locate |
Find a biome, structure, or point of interest | Category names and searchable identifiers vary by edition. |
/loot |
Generate or distribute loot | Loot-table syntax is especially edition-specific. |
/me |
Send an action-style chat message | It changes chat presentation, not the world. |
/msg, /tell, /w |
Send a private message | These are aliases or vary in availability by edition. |
/op |
Grant operator status | Use only for trusted multiplayer administrators. |
/particle |
Create particles | Particle identifiers and position arguments vary. |
/place |
Place configured features or structures | Only certain releases and configurations expose every option. |
/playsound, /stopsound |
Start or stop sounds | Sound identifiers, channels, and target syntax differ. |
/recipe |
Grant or revoke recipes | Check whether the target edition supports recipe management. |
/reload |
Reload data or configuration | Use carefully on servers and with packs that change world data. |
/ride |
Mount or dismount entities | Available forms depend on edition and entity compatibility. |
/say |
Broadcast a message | Useful in command blocks for a server-wide announcement. |
/schedule |
Schedule a function or supported action | Timing syntax and supported targets vary. |
/scoreboard |
Create objectives and manipulate scores | Often forms the state system for minigames and automation. |
/setblock |
Change one block | Can replace, destroy, or keep the existing block where supported. |
/setworldspawn |
Set the world spawn | Accepts a position, with optional coordinate behavior by edition. |
/spawnpoint |
Set a player’s respawn point | Usually targets a player and a location. |
/spreadplayers |
Spread players or entities across an area | Useful for separating teams or starting positions. |
/summon |
Create an entity | Entity identifiers and optional data/components differ. |
/tag |
Add or remove entity tags | Tags let later commands select a persistent group. |
/teleport, /tp |
Move entities to coordinates or another entity | These are commonly used aliases, but argument order differs. |
/time |
Set, add, or query world time | Values such as day, night, noon, and midnight are supported in relevant editions. |
/title |
Display title, subtitle, or action-bar text | Text syntax and channels vary between Java and Bedrock. |
/transfer |
Transfer a player to another server | Requires a compatible multiplayer setup. |
/weather |
Set weather | Common weather values are clear, rain, and thunder. |
/xp, /experience |
Add, set, or query experience | Syntax and whether levels or points are specified differ by edition. |
Java-only commands
The command index identifies these as Java Edition commands. Their presence and syntax still depend on the Java release and server implementation.
| Command | What it is used for |
|---|---|
/advancement |
Grant or revoke advancements. |
/attribute |
Read or modify entity attributes. |
/ban, /ban-ip, /banlist |
Ban players or IP addresses and inspect bans. |
/bossbar |
Create and control boss bars. |
/data |
Inspect or modify entity, block-entity, or storage data. |
/datapack |
Enable, disable, or list data packs. |
/debug |
Control Java debugging traces. |
/defaultgamemode |
Set the default game mode for new players. |
/fillbiome |
Set biome data in a region where supported. |
/forceload |
Keep chunks loaded or query forced chunks. |
/item |
Modify or replace items in entity slots. |
/jfr |
Control Java Flight Recorder profiling. |
/pardon, /pardon-ip |
Remove player or IP bans. |
/publish |
Publish a single-player world to LAN. |
/random |
Generate random values in releases that provide it. |
/return |
Return from a function with a result or control value. |
/save-all, /save-off, /save-on |
Control server-world saving. |
/seed |
Display the world seed. |
/setidletimeout |
Set the idle-player timeout. |
/spectate |
Make a player spectate an entity. |
/team, /teammsg |
Manage teams and send team-only messages. |
/tick |
Control or inspect game ticking in releases that support it. |
/trigger |
Change a trigger objective for a player. |
/worldborder |
Set and manage the Java world border. |
/whitelist |
Manage the server allowlist. |
Bedrock and Education differences
Bedrock-only and Education-only command sets contain additional commands not shared with Java. Education also includes classroom-oriented features, while Bedrock’s syntax uses its own item, component, and target argument forms. A command copied from a Java tutorial may therefore produce an unknown-command error, an invalid-argument error, or a different result in Bedrock.
Best Value
Do not infer support from a command’s name alone. Check /help in the exact world, then inspect the command-specific syntax. The same command can accept different argument order, identifiers, selector filters, JSON text, or coordinate rules across editions.
Starter commands you can adapt
These examples illustrate common jobs. Replace placeholders with values accepted by your edition’s help output.
- Teleport:
/teleport <target player> <destination>moves a player to coordinates or another player. The shorter alias is/tp. - Give an item:
/give @s diamond 64gives the executor 64 diamonds in Bedrock’s current form. - Change weather:
/weather clear,/weather rain, or/weather thunder. - Set time:
/time set day,/time set night,/time set noon, or/time set midnightwhere those names are accepted. - Summon an entity:
/summon <entity> [x] [y] [z]creates the specified entity at the executor’s location or supplied coordinates. - Remove an entity:
/kill <target>selects the player or entity to kill; test selectors carefully before using@aor broad filters. - Set world spawn:
/setworldspawn [x] [y] [z]changes the global spawn position. - Locate a destination:
/locate <category> <thing>searches for a supported structure, biome, or point of interest. - Administer players:
/op <playername>,/kick <playername>, and/ban <playername>require the relevant multiplayer authority, and ban may not be available in every execution context.
How to use a command block
Obtain and place one
- Enable cheats or commands and make sure you have sufficient permission.
- Give yourself a command block with
/give @s minecraft:command_block. - Alternatively, place one directly with
/setblock ~ ~ ~ minecraft:command_block. - Open the block, enter the command, and configure its execution mode before powering it.
Configure execution
- Impulse runs once when powered.
- Repeat runs repeatedly while powered, subject to the game’s tick behavior.
- Chain runs after a preceding command block in a correctly oriented chain.
- Needs Redstone waits for a redstone signal; Always Active removes that requirement.
- Conditional runs only when the preceding block succeeds; Unconditional ignores that result.
Use /execute when a chain must run at a different position, as a different entity, or only when a condition is true. Test one block with a narrow target such as @s before expanding to multiple players or entities.
Command-block restrictions
Command blocks are designed for automation, not unrestricted server administration. Documentation identifies ban, kick, op, deop, stop, and whitelist operations as restricted from command blocks. Run those tasks through an authorized chat or server-console context instead. Keep repeating blocks away from spawn until tested: a malformed repeat command can flood chat, consume resources, or repeatedly alter a large area.
Troubleshoot failed commands
- “Unknown command”: confirm the edition and release, then run
/help. The command may be Java-only, Bedrock-only, Education-only, removed, or disabled by a server. - “You do not have permission”: enable commands in single-player or obtain the necessary multiplayer permission level.
- Invalid argument or syntax: run
/help <command>, follow autocomplete, and check argument order. Do not paste Java syntax into Bedrock or vice versa. - No target found: verify that the selector matches the intended entity, that the player is online, and that the relevant chunks are loaded.
- Nothing happens in a command block: check the block’s redstone mode, orientation, conditional setting, execution location, and output log. A command block runs in its own context, so
@smay select the block’s executor rather than the player you expected. - Unexpected world changes: stop the circuit, restore a backup if available, and test destructive commands such as
/fill,/clone, and/killon a small area or a named target first.
Practical rules for safe command use
- Use the current world’s
/helpoutput instead of an undated command-count list. - Keep edition and version beside every command in a tutorial or command block project.
- Prefer explicit player names, tags, or narrow selectors before using
@aor broad entity filters. - Back up important worlds before testing
/fill,/clone, data changes, or automated repeat chains. - Give operator status only to trusted players and remove it with
/deopwhen it is no longer needed.
The quickest way to find any command
Enable the appropriate permission, type /help, choose the command suggested by autocomplete, and then run /help <command> for its exact arguments. That workflow accounts for edition, release, permissions, and enabled features—the four reasons a copied “complete list” can be incomplete in your world.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
