The commands that matter most on a Bedrock server are the ones that let you discover syntax, control access, move or moderate players, change world rules, automate logic, and shut the server down safely. Start with /help, confirm the permission and cheat requirement for the installed release, and use narrow target selectors before attempting any command that can affect a whole world.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Bedrock servers with free DDoS protection and up to three free backups a day.
Before using any Bedrock command
Bedrock commands are sensitive to edition, server version, permission level and execution context. A command entered in a player’s chat is not the same thing as a command entered in the Bedrock Dedicated Server console. The console is the correct place for server-lifecycle tasks such as stopping a dedicated server, while chat and command blocks require the player’s operator commands permission.
As an Amazon Associate I earn from qualifying purchases.
- Cheats: Microsoft states that cheats must be enabled before commands are used in a world. Enabling cheats disables achievements for that world.
- Operator commands permission: This permission must be enabled to run commands in chat and to access command blocks.
- Syntax: Run
/helpto list commands available to you, or/help <command>to display usage for one command. The output on your server is the final authority for version-specific syntax. - Placeholders: Replace
<player>or<target>with a name or selector. Replacex y zwith three coordinates; relative coordinates use tildes, such as~ ~1 ~.
For a dedicated server, test destructive commands on a copied world or staging instance. In particular, back up before using /kill, /fill, /clone, /clear, broad selector expressions, /kick and /stop.
Command permissions and execution context
Bedrock’s command index assigns permission levels such as Any, Game Directors, Admin and Owner. It also records whether cheats are required. These are separate checks: being an operator does not automatically make every command available in every context.
#1 Best Overall
| Command or group | Permission noted in the reference | Cheat requirement | Typical context | What it changes |
|---|---|---|---|---|
/help, /list, /packstack |
Any | No | Chat or console | Displays information only |
/op, /deop |
Admin | No | Dedicated-server administration | Player permission state |
/allowlist |
Owner-level in the command index | Check the installed release | Dedicated-server console or command | Who may join |
/permission |
Owner | Yes | Dedicated-server administration | Dedicated-server permissions |
/stop |
Owner | Yes in the current index | Dedicated-server console | Server lifecycle |
/kick |
Game Directors | No | Chat or console | Removes a player temporarily |
/gamerule |
Use the current command help for your role | No | Chat or console | World behavior rules |
| Many player and world commands | Often Game Directors | Varies by command | Chat, command block or console | Player state or world state |
If a command is rejected, do not assume the syntax is wrong. First check that you have the required role, operator commands is enabled, cheats are enabled when required, and you are using the correct context.
Discovering commands and diagnosing a server
/help: the first command to try
/help lists every command you can run. /help teleport, for example, shows the accepted forms for teleporting, including optional arguments that can differ between releases. Use this after updates and before copying an example from an older guide.
Recommended Free Tools
/list: see who is online
Use /list to display players currently connected. It is read-only and does not require cheats, making it useful for choosing a precise target before a moderation action.
/packstack: inspect behavior and resource packs
/packstack prints the client or server pack stack to chat. It helps identify which packs are active when a command, function or custom behavior appears not to work as expected.
Access control and moderation
Granting and revoking operator status
- From the dedicated-server console, run
/op <player>with the player’s exact name. - Ask the player to reconnect or retry the command if their permissions do not update immediately.
- Remove access with
/deop <player>when the administrative task is complete.
The command index lists both /op and /deop as Admin-level and not requiring cheats. Grant the smallest level of access necessary; operator status can expose destructive commands.
Allowlisting players
The Bedrock Dedicated Server guide identifies /allowlist add <GamerTag> as the easiest way to add someone. GamerTags must match exactly, including capitalization. Use the corresponding remove, list and status actions shown by /help allowlist on your release.
Allowlisting is an access gate, not a substitute for operator permissions: a person can be allowed to join without being allowed to administer the world.
Managing dedicated-server permissions
/permission list, /permission set and /permission reload manage dedicated-server permission data. The command index marks this command as Owner-level and requiring cheats. Confirm the exact set arguments with /help permission before changing a live server.
Removing a player
/kick <player> disconnects a player without changing the allowlist or banning them permanently. It is reversible by simply allowing the player to reconnect. Because a selector can match more than one person, use an exact name when the action is intended for one player.
Communicating with players
/say <message>sends a server-wide announcement./tell <target> <message>sends a private message./tellraw <target> <raw JSON message>sends formatted text when you need colors or click events./title <target> ...and/titleraw <target> ...display title overlays; use/help titleor/help titlerawfor the installed syntax.
Target selectors: control who is affected
Selectors make commands scalable but also increase the chance of affecting the wrong players. Common Bedrock selectors include:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →| Selector | Scope | Safer use |
|---|---|---|
@s |
The command’s current executor | Functions or command blocks that should act on themselves |
@p |
Nearest player | Short-range interactive commands |
@a |
All players | Announcements or deliberate server-wide effects |
@e |
All loaded entities | Only with restrictive filters such as type, distance or name |
@r |
A random player | Games and chance-based mechanics |
Before using @a or @e with /clear, /kill, /effect, /tp or block-editing commands, run a harmless diagnostic such as /list or a narrowly scoped message. A selector that matches zero entities is usually safer than one that matches more than intended.
Player movement and state
Teleporting safely with /teleport or /tp
/teleport (aliased as /tp) can move yourself or a target to coordinates or another entity. Depending on the form, it also accepts rotation, a facing direction or entity, and a check-for-blocks option.
- Preview the destination and identify the target:
/listor an exact player name is safer than a broad selector. - Teleport to coordinates with the syntax shown by
/help teleport, supplyingx y zor relative coordinates. - When moving a player to another entity, use the entity-target form documented in your release.
- Use the optional check-for-blocks argument when available to prevent placement inside obstructed terrain, and use rotation or facing arguments when orientation matters.
Teleportation is immediately reversible only if you recorded the original location. For staff moves, note the starting coordinates or use a controlled hub destination.
Changing game mode
/gamemode <mode> [target] changes a player’s mode. Supply the target explicitly when changing someone else’s mode. The available modes and cheat requirement are release-sensitive, so confirm them with /help gamemode and the current command index.
Effects and inventories
/effectadds, removes or clears status effects. Restrict the target and duration; an accidental@acan change every player’s combat or movement state./givegrants items, while/clearremoves items. Treat/clearas destructive and test its item and quantity arguments on a backup./replaceitemchanges a specified inventory or equipment slot. Verify the slot path with/help replaceitem./spawnpointsets a player’s spawn point;/clearspawnpointremoves it. Use an exact target to avoid changing a whole group.
World rules, time and weather
Querying and setting gamerules
/gamerule queries or sets Boolean and integer rules. The reference specifically includes commandblockoutput and dodaylightcycle, and states that /gamerule does not require cheats.
- Query a rule first using the form shown by
/help gamerule. - Change only the named rule and value, for example the daylight-cycle rule when you need a fixed time.
- Record the old value so another administrator can restore it.
Disabling command-block output can reduce chat noise, while disabling the daylight cycle changes the world’s ongoing behavior. These are world-state changes, not player-only changes.
Difficulty, time and weather
/difficultyselects Peaceful, Easy, Normal or Hard. Check the current syntax and consider how hostile mobs and player survival will change./time set day,noon,night,midnight,sunriseorsunsetsets the world’s time using the documented TimeSpec values./weathersets weather;/toggledownfalltoggles downfall. These affect the world rather than one player./mobeventcontrols which mob events run. Use/help mobeventto see event names accepted by your release./tickingareaadds, removes or lists areas that continue ticking. Keep areas small and intentional because they can keep redstone, entities or command systems active away from players.
Building, automation and command logic
/execute: conditional command chains
/execute runs a nested command with a changed executor or origin and can add conditions. Microsoft examples use forms such as as, positioned as and if block. Build and test one clause at a time; a wrong executor or position is a common reason an otherwise valid command appears to do nothing.
Functions and scoreboards
/function runs commands stored in a behavior-pack function file, which is more maintainable than a long row of command blocks. /scoreboard creates objectives and manipulates scores, providing persistent state for minigames, timers, teams and conditional systems. Keep objective names documented and remove unused objectives from production worlds.
Editing blocks and regions
/setblockchanges one block./fillchanges a region according to a block and mode./clonecopies one region to another location.
These commands can alter thousands of blocks in one operation. Start with a tiny test region, specify coordinates carefully, and work from a backup. A region edit is not as easily reversible as a player permission change.
Entities, tags and structures
/summoncreates an entity at a location./tagattaches or removes labels that selectors and functions can use./eventtriggers an entity event when the entity supports it./structuresaves or loads structures, useful for repeatable builds and templates.
Use tags to make selectors precise, such as selecting only entities marked for a particular minigame. Remove temporary tags and entities when an event ends.
Saving and stopping a dedicated server
/save
/save configures or checks save behavior on a dedicated server. Its exact subcommands and arguments are version-sensitive; run /help save on the installed release before changing save settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
/stop
Use /stop from the dedicated-server console to shut the server down cleanly. The current command index marks it Owner-level and requiring cheats. Warn players first with /say, wait for active building or transfers to finish, then issue the command in the console rather than relying on a process kill. Do not confuse a clean stop with /kick, which only disconnects a player.
A practical admin workflow
- Identify the context: decide whether the command belongs in chat, a command block, a function or the dedicated-server console.
- Check permissions: confirm operator commands is enabled and that your role meets the command’s level.
- Inspect syntax: run
/help <command>on the actual server version. - Narrow the target: prefer an exact player name or a filtered selector over
@aor@e. - Test reversibility: record old gamerules, coordinates or permissions; back up before region and inventory edits.
- Announce disruptive actions: tell players before changing difficulty, weather, time or stopping the server.
- Verify the result: query the rule, list players, inspect the pack stack or run a harmless follow-up command.
This workflow matters because Bedrock command syntax and requirements change over time. A command copied from an older tutorial can fail even when the underlying operation is still supported; the in-game help output tells you what your current server accepts.
Frequently Asked Questions
Do Bedrock server commands always require cheats?
No. The command index marks several administrative and diagnostic commands, including /help, /list, /op, /deop, /kick and /gamerule, as not requiring cheats, while other commands do. Check /help <command> and your current permission level.
How do I stop a Bedrock Dedicated Server safely?
Warn players, allow current activity to finish, then run /stop in the dedicated-server console. The current index lists /stop as Owner-level and requiring cheats.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Why does an allowlist entry not work?
The GamerTag must match exactly, including capitalization. Recheck it with the allowlist listing command and compare the spelling with the player’s account name.
What is the safest way to test a destructive command?
Use a copied or staging world, begin with a narrow target or small region, and record the original state. This is especially important for /kill, /clear, /fill, /clone and broad selectors.
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.
