List of Minecraft Commands: A Practical Guide
Explore a comprehensive list of Minecraft commands with practical examples, cheatsheets, and step-by-step guidance for Java and Bedrock editions.

Here is a concise overview: Minecraft commands unlock in-game actions, world editing, item management, and server controls. This quick answer highlights how to invoke commands across Java and Bedrock editions, what each command does, and where to find reliable syntax references. Whether you're building, surviving, or running a small server, mastering the core set of commands dramatically speeds up your workflows. According to Craft Guide, a focused core of commands yields the most value for players of all skill levels.
In-game command fundamentals
Minecraft commands are the backbone of automation, world manipulation, and player control. They start with a slash (/) and use selectors to target players or entities, making it possible to perform precise actions in seconds. In this section, we cover the core ideas that power most commands: selectors, targets, and the basic command structure. For example, you can give yourself items, move between coordinates, or switch game modes with concise syntax.
/give @p minecraft:stone 64/tp @p 100 64 -20/gamemode creative @pThese examples show how you can access inventory, teleport, and switch modes quickly. Remember that some commands require cheats to be enabled or a server console context to work, depending on your setup. Craft Guide's analysis, 2026, notes that most players rely on a handful of commands for day-to-day play, which is why this guide emphasizes a core starter set.
Edition differences: Java vs Bedrock
Minecraft Java Edition and Bedrock Edition share many commands, but some syntax and capabilities differ. Java often requires more explicit selectors and NBT data for advanced edits, while Bedrock leans on simpler or differently named commands for similar effects. The following examples illustrate how the same goal can look in each edition:
# Java Edition (selector-based, advanced):
execute as @a at @s run say Hello from Craft Guide# Bedrock Edition (simplified in-chat command):
/say Hello from Bedrock# Alternate Bedrock approach (execute doesn't match Java exactly):
/tell @a Hello from Bedrock usersIf you need deeper parity, consult the Minecraft Wiki as it documents edition-specific differences and recommended patterns for cross-edition builds. Craft Guide analysis shows that players often start with the simplest commands and progressively adopt edition-specific syntax as they grow more comfortable.
Core player commands: essentials you’ll use daily
For most players, a small set of commands covers 90% of daily needs: giving items, teleporting, clearing inventories, and setting game modes. This section demonstrates practical uses and explains when to choose one approach over another. The examples below assume cheats are enabled or you’re in a server console/command block context. Use the commands responsibly in multiplayer environments to avoid disrupting others.
/give @p minecraft:diamond 1/tp @p 128 70 -256/kill @e[type=!player]These commands help you acquire gear quickly, relocate yourself, and manage mobs in a controlled way. Always verify permissions in your world or server to ensure commands execute as intended.
World editing commands: shaping the terrain
World editing commands let you sculpt landscapes or populate areas with blocks. The most common tools are /setblock and /fill, which let you place or override blocks with precision. The following examples show how to create a simple stone platform and fill a 10x10 area with stone: /setblock 0 64 0 minecraft:stone
/setblock 0 64 0 minecraft:stone/fill -5 64 -5 5 64 5 minecraft:grass_blockFor complex builds, consider breaking edits into smaller chunks and testing results in a local world before applying to larger regions. Craft Guide’s practical testing workflow emphasizes incremental changes and frequent saves to prevent unwanted terrain modifications.
Admin and server management: controlling the environment
Server administration commands are essential for multiplayer worlds and server operators. While some actions are done through the server console, others use in-game commands that require operator permissions. The following console-oriented examples illustrate starting and stopping the server, listing players, and backing up progress:
# Start server (example, adjust memory as needed)
java -Xmx4G -Xms2G -jar server.jar nogui# Stop server gracefully
stop# List online players on the server console
listRegular maintenance tasks, including saves and backups, help maintain world integrity during heavy edits or player activity. Craft Guide analysis suggests coupling commands with periodic saves to reduce the risk of data loss when performing mass changes.
Safe usage patterns and troubleshooting
To avoid accidental damage or unwanted changes, practice a set of safety habits: test commands in a private world, enable cheats in a controlled environment, and use gamerules to constrain behavior (for example, doMobSpawning and keepInventory). If a command yields an unexpected result, step back, revert, and re-run with a smaller scope. You can observe command outputs and server logs to fine-tune parameters and understand how the game interprets your input.
#gamerule to prevent mob spawns
/gamerule doMobSpawning false# keep inventory when you die (single-player or server with operator rights)
/gamerule keepInventory trueUnintended edits are easier to recover from when you maintain a habit of frequent saves, versioned backups, and a test realm for experimentation.
Finding more commands and learning resources
Minecraft ships with dozens of commands across categories like movement, world editing, and administration. When you want to expand beyond the core set, consult the in-game help (when available) and the official Minecraft Wiki, which documents command syntax, parameters, and edge cases. Craft Guide recommends starting with practical tutorials that pair commands with real-world goals (e.g., automating a farm, creating a guarded shelter, or managing a small server).
Practical example: building a controlled drop using commands
A common automation task is creating a controlled item drop using a combination of /summon, /setblock, and redstone logic. For example, you can summon a drop timer, fill a drop chamber, and trigger with a pressure plate. The approach below shows a simple, safe method to implement a timed drop:
# Set up a drop block at coordinates
/setblock 10 60 10 minecraft:air# Create a drop item hosing mechanism (highly simplified)
/summon minecraft:item ~ ~ ~ {Item:{id:"minecraft:stone",Count:1b}}Keep the logic modular and test each step separately to avoid cascading errors in larger builds. Craft Guide’s method favors clear, repeatable steps with rollback points to simplify troubleshooting.
Quick-start recap and next steps
By now you should have a solid grasp of the most common in-game commands, differences between Java and Bedrock, and practical patterns for world editing, item handling, and server management. Practice the fundamentals in a small, contained world before expanding to more ambitious projects. As you gain confidence, combine commands with command blocks and data packs to extend functionality without sacrificing stability.
Steps
Estimated time: 60-90 minutes
- 1
Enable cheats and prepare world
Open your world and enable cheats, or ensure you have operator permissions on a server. This first step ensures that subsequent commands will be accepted by the game. Create a small test area to verify each command’s effect without risking your main build.
Tip: Test each command separately in a copy of your world to avoid unintended changes. - 2
Learn core in-game commands
Begin with the three most-used commands: /give, /tp, and /gamemode. Practice basic item giving, simple teleportation, and mode switching in a safe area.
Tip: Keep a cheat sheet handy with the exact syntax for your edition. - 3
Experiment with world editing
Try /setblock to place a single block or /fill to modify a region. Work in small sections and preview changes before expanding.
Tip: Use coordinates in decimal form and verify them with your in-game cursor. - 4
Layer in admin commands
On a server, practice /list, /kick, and /stop. These are essential for maintaining order and restarting sessions without data loss.
Tip: Always back up before making bulk changes. - 5
Document your command workflows
Record your common patterns and settings (e.g., gamerules and frequently used commands). This helps you reproduce results and onboard teammates quickly.
Tip: Version your command sheets with a simple changelog. - 6
Test in a controlled scenario
Create a small replica area to test complex sequences (auto-run command blocks, timing, and chained effects). Verify outcomes before applying to the main world.
Tip: Break complex sequences into discrete tests and combine only when each part passes. - 7
Expand to advanced commands
Once comfortable, explore /execute, /data, and resource-pack or data-pack integrations to extend functionality. Maintain safety and backups.
Tip: Begin with well-documented tutorials and gradually integrate new concepts.
Prerequisites
Required
- Required
- Cheats enabled or server operator accessRequired
- Familiarity with basic keyboard/mouse controlsRequired
- Access to a test world or serverRequired
Optional
- Text editor or notes for command referencesOptional
Commands
| Action | Command |
|---|---|
| Start server (console)Run from server directory; applicable to Java Edition server instances | java -Xmx4G -Xms2G -jar server.jar nogui |
| Stop server gracefullyStops server cleanly, saving all worlds | stop |
| List online playersWorks in server console to display current players | list |
| Give item to playerIn-game or command block (Java Edition) | /give @p minecraft:diamond 1 |
| Teleport a playerIn-game; can target more precise locations | /tp @p 100 64 -20 |
| Set a gameruleAffects creature spawning in the world | /gamerule doMobSpawning false |
People Also Ask
What is the quickest way to learn Minecraft commands?
Start with the core set: /give, /tp, and /gamemode. Practice in a dedicated test world, and gradually add commands as you verify behavior. Use the Minecraft Wiki as a reference and keep a personal cheatsheet for quick access.
Start with the basics: give, teleport, and game mode. Practice in a test world and build from there; use a cheatsheet for quick reference.
Are commands the same in Java and Bedrock?
Many commands are similar, but syntax and capabilities differ between editions. Always check edition-specific examples and test in your version to avoid surprises.
Commands share concepts, but the exact syntax can differ between Java and Bedrock. Always verify for your edition.
Can I use commands in single-player without enabling cheats?
Cheats must be enabled for most commands to work in single-player. In creative mode, you typically have passing access to command features, but survival may require an enabled cheats toggle.
Usually you need cheats enabled to use commands, especially in survival mode.
Where can I find the full list of commands?
The full list is documented on the Minecraft Wiki and integrated community guides. This article also serves as a practical reference with runnable examples and editor-friendly patterns.
You can find the full command list on the Minecraft Wiki; this guide also covers practical examples.
Do commands affect performance or cause lag?
Mass edits or complex executions can impact performance, especially on servers. Use commands in smaller batches and monitor server load to minimize lag.
Yes, big edits can slow things down; test in small batches and watch performance.
How do I reset a command block or script?
To reset, disable the command chain, clear the block, or delete and re-create it with updated logic. Always back up before making changes to command blocks.
Reset by disabling or replacing the command block, and back up first.
The Essentials
- Master core commands: /give, /tp, /gamemode
- Differentiate Java vs Bedrock syntax and adapt accordingly
- Use /setblock and /fill for efficient world editing
- Great server control relies on console commands and gamerules
- Always test and back up before large changes