Commands

On top of every vanilla Bedrock command, Endstone registers a small set of built-in commands for administering the server, managing bans, and inspecting what is running. They behave like any other command: type them in the server console or in-game chat (prefixed with /), and they respect the permission nodes listed below.

Reading the usage syntax

Endstone prints command usage in the notation used throughout this page:

Where two usages are listed for one command, either form is accepted - Endstone picks the matching overload based on what you type.

Ban management

Commands for banning and pardoning players and IP addresses. Bans are persisted across restarts.

ban

Bans a player from the server. If the player is online they are kicked immediately. Accepts either a raw name or an online player; when an online player is matched, their UUID and XUID are recorded with the ban so it survives a name change.

• Usage: /ban <name: str> [reason: message] or /ban <name: player> [reason: message]
• Permission: endstone.command.ban

ban-ip

Bans an IP address. You can pass a literal IPv4/IPv6 address, or the name of an online player to ban the address they are currently connected from. Every online player sharing that address is kicked.

• Usage: /ban-ip <address: str> [reason: message] or /ban-ip <name: player> [reason: message]
• Permission: endstone.command.banip

banlist

Lists current bans. With no argument it shows both banned players and banned IPs; pass players or ips to show just one. Each entry shows who was banned, who issued the ban, and the reason.

• Usage: /banlist (ips|players)
• Permission: endstone.command.banlist

pardon

Removes a player from the ban list. Does nothing if the player is not banned.

• Aliases: unban
• Usage: /pardon <name: str>
• Permission: endstone.command.unban

pardon-ip

Removes an IP address from the ban list. The address must be a valid IPv4 or IPv6 address.

• Aliases: unban-ip
• Usage: /pardon-ip <address: str>
• Permission: endstone.command.unbanip

Server management

Commands for controlling the server lifecycle and reloading configuration.

reload

Reloads the server configuration, functions, scripts, and plugins. Every plugin is disabled and re-enabled; an admin broadcast confirms when the reload completes.

• Aliases: rl
• Usage: /reload
• Permission: endstone.command.reload

restart

Restarts the server. Players are notified with an admin broadcast, a restart marker is written to the server directory, and the server shuts down so the launcher can bring it back up.

• Usage: /restart
• Permission: endstone.command.restart

Information

Commands for inspecting the server, its plugins, and the world.

version

Shows the server and Minecraft version. With a plugin name, shows that plugin's version, description, website, and authors instead.

• Aliases: ver, about
• Usage: /version or /version [plugin: PluginName]
• Permission: endstone.command.version

plugins

Lists every installed plugin and how many there are. Enabled plugins are shown in green, disabled plugins in red.

• Usage: /plugins
• Permission: endstone.command.plugins

status

Reports the live health of the server: uptime, current and average TPS (with MSPT), thread count, used and total memory, and per-dimension loaded-chunk and entity counts.

• Usage: /status
• Permission: endstone.command.status

seed

Outputs the world seed.

• Usage: /seed
• Permission: endstone.command.seed

devtools

Opens the Endstone DevTools window. Can only be run from the console.

• Aliases: dev
• Usage: /devtools
• Permission: endstone.command.devtools

Summary

Related

• Permissions - the nodes that govern these commands and how defaults work.