Repository navigation
Managing Players From The Command Line
github-actions[bot] edited this page Oct 1, 2026
·
2 revisions
From the web UI's Players page, or the command line:
craft-conductor player list
craft-conductor player op Steve
craft-conductor player deop Steve
craft-conductor player kick Griefer --reason "cool it"
craft-conductor player ban Griefer --reason "griefing spawn"
craft-conductor player pardon Griefer
craft-conductor player ban-ip 203.0.113.9
craft-conductor player whitelist-on
craft-conductor player whitelist-add AlexWhile the server runs, these are sent as the normal console commands (from the
command line this goes over RCON; the web UI doesn't need it). While it's stopped,
Craft Conductor edits ops.json, banned-players.json, banned-ips.json, whitelist.json
and server.properties directly, and the changes apply when the server starts. For
that it looks up player UUIDs from usercache.json or Mojang, or computes the
offline UUID when online-mode=false. Kicking, and IP-banning by player name, need
the server running.
User manual
- Start here
- What it can and can't do
- Getting started
- Creating a server
- Messages
- Your servers
- Dashboard
- Console
- Players
- Mods
- Updates
- Backups
- Java
- Settings
- Playing with friends
- Joining a friend's server
- Remote access and phones
- People and what they may do
- Craft Conductor settings
- Troubleshooting
- Getting help
Power users
- Power users: start here
- Configuration (craft-conductor.toml)
- Building servers from the command line
- Running it forever
- Linux servers without a screen
- Managing players from the command line
- Java in detail
- How an upgrade works
- Updating Craft Conductor
- Mods that block third-party downloads
- Security
- Other ways to install
- For maintainers
- Where Craft Conductor keeps things
- Command line