Minecraft Bedrock Server Admin Commands and How to Use Them

Minecraft Bedrock server administration is handled with commands entered either in player chat or in a dedicated server console. Start with help (in the console) or the running version’s command reference, then use the smallest permission level that accomplishes the job. The commands most administrators need are list, op, deop, kick, ban, allowlist, teleport/tp, gamerule, time, weather, difficulty, and stop.

Syntax and availability vary between Bedrock releases and server builds. A command can also be blocked by the caller’s permission level, the server’s Allow Cheats setting, or server.properties. Treat the live help output and the official reference that matches your installed version as the authority before changing a world or disconnecting a player.

What are Bedrock server admin commands, and where do I enter them?

Bedrock commands are text instructions that query or change a world, player, or dedicated server. In in-game chat, type a forward slash before the command, such as /list. In a dedicated-server console, the official getting-started instructions show commands without the slash, such as help or stop; follow the syntax displayed by your panel or console.

Chat is convenient when you are already playing, but the result is visible in the game and is subject to the player account’s permissions. The console gives an operator a central audit trail and remains available when no administrator is in the world. Console output also reveals the exact command set shipped with that server build.

How do arguments change a command?

The first word selects the command. Words after it are arguments that specify a value, target, or mode. For example, /difficulty easy chooses the Easy difficulty, /weather clear requests clear weather, and /time set 1000 sets the world time to 1,000 ticks. A teleport command needs a destination and may also need a target selector or player name.

Do not assume that a Java Edition example or an older Bedrock post uses the same grammar. Run help <command> when your build supports that form, or use the closest command-specific help entry, then compare it with the version-matched official Bedrock reference.

Why does a Bedrock command say I do not have permission?

Permission errors normally mean that the command requires a higher player permission level, requires Allow Cheats, or is being run in a server configuration that does not permit it. The official command reference identifies a required permission level and a cheats-required field for each command. list is available to any user, while commands such as allowlist, stop, and teleport require more access.

How do I grant and remove operator status?

On a dedicated server, enter op <playername> in the console to grant operator status. To remove it, use deop <playername>. Use the exact account name shown by list; a typo creates the impression that the command failed or affected nobody.

Give operator access only to named, trusted administrators. An operator can use world-changing and lifecycle commands, so a shared account or a casually granted role makes griefing and accidental shutdowns much more likely. Remove access promptly when a moderator no longer needs it.

What should I check before changing cheats or permissions?

• Confirm whether you are in chat or the console and use that interface’s slash convention.
• Check the command’s required permission level in the running help output or official reference.
• Check whether the command is marked as requiring cheats.
• Verify that the account or console session is connected to the intended world and server.
• Test with a harmless command such as /list before running a destructive one.

Which Bedrock commands cover everyday administration?

The following groups cover discovery, moderation, player support, world settings, and server lifecycle work. Availability and argument names can change, so use the table as a map to the right command, not as a substitute for the help output on your installation.

Discovery and visibility commands

Command	What it does	Example and cautions
help	Lists available console commands and, where supported, provides syntax help.	help shows the build’s command list. Try help <command> for details.
/list	Shows players currently connected.	Available to any user according to the official reference; useful for checking a name before moderation.
/locate	Finds a nearby biome or structure when that feature is supported by the installed version.	Check the live syntax because supported targets differ by release.

Access and moderation commands

Command	Purpose	Operational notes
/op <player>	Grants operator status.	Use only for trusted administrators; confirm the exact player name.
/deop <player>	Revokes operator status.	Run it immediately when elevated access is no longer justified.
/kick <player>	Removes a player from the server.	The player can reconnect unless another control, such as an allowlist or ban, prevents it.
/ban <player>	Bans a player where the running command set supports banning.	Confirm the exact syntax and ban storage behavior in your build before relying on it for enforcement.
/allowlist	Manages which players may connect.	Subcommands and enable/disable syntax must be checked in the installed reference and in server.properties.

Player and world-support commands

Command	Purpose	Example
/teleport or /tp	Moves an entity or player to specified coordinates or another target.	Use the syntax shown by help teleport; target selectors and coordinate arguments are significant.
/gamerule	Reads or changes a game rule.	A daylight-cycle change is commonly written as /gamerule doDaylightCycle false; verify capitalization and available rules on your build.
/time	Queries or changes world time.	/time set 1000 sets a numeric time value; use the supported query or preset form for your version.
/weather	Changes the current weather.	/weather clear requests clear weather. Duration or alternate weather arguments may be version-dependent.
/difficulty	Sets the world difficulty.	/difficulty easy is an example; the caller must meet the command’s permission and cheats requirements.

Lifecycle command

Command	Purpose	Safe use
stop	Shuts down a dedicated server.	Use the console command for a clean shutdown before maintenance or backups. Do not close the process window as a substitute.

How do I use a command without changing the wrong world?

Separate harmless discovery from commands that alter players or persistent world state. A short verification routine prevents most costly mistakes.

1. Identify the interface. In chat, begin with /; in the dedicated console, use the console’s documented form, normally without it.
2. Confirm the target. Run /list in chat or list in the console and copy the player name exactly. For coordinates or selectors, re-read every argument before submitting.
3. Read the live syntax. Use help and the command-specific help form available in your build. Check the matching official Bedrock command reference if the output is abbreviated.
4. Check authority. Make sure the caller has the required permission level and that Allow Cheats is enabled when the command requires it.
5. Run the least disruptive test. list is a safe connectivity check. A world-changing command should be tested in a copy of the world when practical.
6. Observe the response. Read the success or error text. A command that returns an error should not be repeated with guessed arguments.
7. Record changes. Note altered gamerules, difficulty, time, weather, allowlist entries, and operator assignments so another administrator can understand the current state.

How do I install and operate a Bedrock dedicated server?

Use the official Bedrock Dedicated Server package and follow its startup instructions. The administrative sequence below keeps configuration, permissions, testing, and shutdown in a predictable order.

1. Install the package. Download the official Bedrock Dedicated Server release appropriate for your operating system and complete its documented first-start process.
2. Review server.properties. Set the intended game mode and other server options before inviting players. This file also controls important connection and allow-list behavior.
3. Start the server. Wait for the console to report that it is ready, then enter help to see the commands exposed by that build.
4. Create a limited administrator group. Grant op <playername> only to trusted people who actually need elevated commands. Keep a written record of who has that status.
5. Perform a harmless test. Run list and, if needed, a read-only help query. Verify that the expected world and player session are present.
6. Apply administration changes. Use moderation, allowlist, teleport, gamerule, time, weather, or difficulty commands only after checking their current syntax and requirements.
7. Stop cleanly. Enter stop in the console before maintenance. A clean stop reduces the chance of incomplete writes and gives you a stable point for a world or configuration backup.

How does server.properties relate to commands and the allowlist?

server.properties is the dedicated server’s persistent configuration file. It controls options such as game mode and which players may connect, while the allowlist command is the live administrative interface for managing permitted players when that feature is enabled.

When should I edit the file?

Use the file for settings that should survive a restart, and use commands for immediate administration. Make a backup before editing, keep the syntax exactly as documented for your release, and restart or reload only when the server instructions say the change is recognized. If an allowlist behaves unexpectedly, inspect both the file’s allow-list setting and the command form shown by the running server.

How do I avoid locking out administrators?

Before enabling an allowlist, confirm that every administrator’s account name is entered exactly as the server expects. Keep a console session available while testing, and do not remove the account you need for recovery until another trusted administrator has successfully connected.

Is in-game chat or the server console better for administration?

Neither interface is universally best. Chat is faster for a moderator who is already in the world; the console is safer for server-wide changes, startup diagnostics, and shutdown because it is separated from player chat.

Consideration	In-game chat	Dedicated console
Entry format	Use a leading slash, such as /weather clear.	The getting-started guide shows console commands such as help without a leading slash.
Convenience	Immediate while playing; no context switch.	Requires access to the host, terminal, or control panel.
Visibility	Messages may be visible to players and scroll away.	Provides a centralized operational log.
Permissions	Uses the connected player’s role and cheats rules.	Uses the console’s administrative authority, but still follows the build’s command set.
Best use	Quick checks, player support, and routine moderation by an authorized moderator.	Configuration checks, operator management, backups, maintenance, and stop.

Should I self-host or use managed Bedrock hosting?

Self-hosting gives you direct control over files, logs, networking, and backups, but you must maintain the operating system, firewall, uptime, and recovery process. Managed hosting can simplify those tasks through a panel, but you trade some low-level control for the provider’s maintenance schedule and feature limits.

Axis	Self-hosted server	Managed server
Control	Direct access to the Bedrock process, server.properties, world files, and console.	Access depends on the provider’s panel and exposed settings.
Maintenance	You apply server updates, operating-system patches, and security fixes.	The provider may handle host maintenance; confirm what remains your responsibility.
Networking	You configure ports, firewall rules, NAT, and connectivity tests.	The provider generally supplies a reachable endpoint, subject to its network design.
Backups	You schedule, verify, and store world and configuration backups.	Backup frequency, retention, and restore controls vary; read the plan’s terms.
Cost and predictability	Uses your hardware, electricity, and connection; costs depend on your setup.	Usually a recurring hosting charge; the exact amount and limits depend on the provider.

Whichever model you choose, retain an independent copy of the world and configuration. A hosting dashboard is not a substitute for a restore procedure you have actually tested.

How should I assign permissions securely?

Broad operator access is convenient but increases the blast radius of a stolen account or an accidental command. Narrow assignment keeps routine moderation separate from world and server lifecycle control.

Use role separation

• Give a chat moderator only the access needed for the community’s moderation policy.
• Reserve op for administrators who must change gamerules, teleport players, edit access, or stop the server.
• Use named accounts rather than a shared login so every operator can be removed individually.
• Review the operator list after staff changes and run deop <playername> when access should end.

Protect high-impact commands

stop, teleport, gamerule, difficulty, allowlist, and operator-management commands can affect everyone. Require a second administrator’s confirmation for irreversible moderation or maintenance actions, and announce scheduled shutdowns before using stop.

Why is a Bedrock command unknown or behaving differently?

Unknown-command errors usually indicate a spelling error, an unsupported command in that build, or syntax copied from a different edition or release. The fix is to inspect the server’s own command list instead of guessing.

“Unknown command”

1. Run help in the console, or open the in-game help available to your account.
2. Check spelling, capitalization, and whether the command is an alias such as /tp for /teleport.
3. Compare the arguments with the official reference for the installed Bedrock version.
4. If the command is absent, do not substitute a Java Edition form; use a supported Bedrock command or an administrative setting instead.

“You do not have permission”

Check the caller’s role, the command’s required permission level, and its cheats-required field. On a dedicated server, verify that you are using the intended operator account and that the server configuration has not changed.

Chat works but the console fails, or the reverse

Confirm the interface convention first: chat normally requires /, while the dedicated-server guide presents console commands without it. Then check whether the two sessions are connected to the same world and server process; a local single-player world and a remote dedicated server can expose different command sets and permissions.

The allowlist blocks the wrong people

Inspect server.properties for the allow-list setting, verify names exactly, and use the allowlist subcommand documented by the running server. Keep a console connection while testing so you can correct an entry without relying on a player who has already been denied access.

A command produced an unexpected result

Read the full response, check every target and coordinate argument, and compare the requirement fields for that command. Available entries and requirements can change between releases, so validate the command against the running build before repeating it.

What is the safest maintenance routine for a Bedrock server?

Plan maintenance around a clean shutdown and a known-good backup rather than killing the process. This protects both the world and the configuration that determines who can connect.

1. Announce the maintenance window to players.
2. Use list to see who remains connected and handle any active moderation issue.
3. Enter stop in the dedicated console and wait for the process to finish.
4. Copy the world directory and server.properties to a separate backup location.
5. Apply the server or configuration change according to the release instructions.
6. Start the server, run help, and verify that expected commands are present.
7. Test connectivity, allowlist behavior, and a harmless command before reopening the server.

Keep at least one backup that is not on the same disk as the live world, and periodically verify that it can be restored. The command documentation describes stop; backup retention and restore testing are operational safeguards you must arrange yourself.

How can I keep commands compatible after an update?

Record the Bedrock version and dedicated-server build alongside your operating notes. After an update, run help, compare high-impact commands with the matching official reference, and retest permissions, allowlist behavior, and any automation that sends commands.

Do not treat an old tutorial’s syntax as permanent. A command may remain familiar while its accepted arguments, permission requirement, cheats requirement, or availability changes. Version-checking is especially important for locate, allowlist, and commands that use selectors or coordinate forms.

What should a new administrator do first?

Start in the console with help, review server.properties, and identify the trusted administrators who genuinely need op. Test with list, document the command forms shown by your build, and make a clean-stop backup routine before inviting a larger community. This approach keeps everyday moderation quick while limiting the consequences of a wrong target, stale syntax, or overbroad permission.

Frequently Asked Questions

Can I remove operator access without restarting the Bedrock server?

Yes. Use deop <playername> from an authorized chat session or the dedicated console, then confirm the account can no longer perform an operator-only command. Keep another trusted administrator connected so a mistaken removal can be corrected immediately.

Is /tp different from /teleport on Bedrock?

They are commonly presented as equivalent names for moving entities, but the accepted targets and coordinate arguments still depend on the installed command set. Check the live help entry before using either form for a group of players.

How can I verify that an allowlist change persisted?

After changing the allowlist, inspect the corresponding setting and entries in server.properties and perform a controlled reconnect with a permitted account. Keep the console available during the test so you can correct a name or setting without locking yourself out.

What information should I include in an administrator handoff?

Record the Bedrock and server-build versions, the console access method, the current operator names, allowlist status, important gamerules, backup location, and the exact help syntax for commands your staff uses. Including the last clean shutdown and backup time makes recovery much faster.