{"id":21061,"date":"2026-05-28T07:46:50","date_gmt":"2026-05-28T07:46:50","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/romestead-console-commands\/"},"modified":"2026-05-28T07:46:50","modified_gmt":"2026-05-28T07:46:50","slug":"romestead-console-commands","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/romestead-console-commands\/","title":{"rendered":"Romestead Console Commands Cheat Sheet: kick, ban, say, save, and Every Admin Command"},"content":{"rendered":"

Romestead’s dedicated server accepts admin commands on standard input<\/strong> \u2014 no RCON daemon, no external client, no remote console protocol. If you’ve got console access to the running server (the panel Console<\/strong> tab on managed hosting, or an attached screen<\/code> session on a self-hosted box), you can run any of the commands below by typing and pressing Enter.<\/p>\n

This is the complete reference, drawn from the official Beartwigs Docker setup that ships with the dedicated server tool.<\/p>\n

Player Management<\/h2>\n\n\n\n\n\n\n\n\n
Command<\/th>\nWhat it does<\/th>\nWhen to use it<\/th>\n<\/tr>\n<\/thead>\n
list<\/code><\/td>\nPrint every currently connected player<\/td>\nBefore kicking or banning \u2014 copy the exact name from this output<\/td>\n<\/tr>\n
kick <PlayerName><\/code><\/td>\nDisconnect a player; they can rejoin<\/td>\nSoft warning for trolling, AFK kick, or troubleshooting a stuck client<\/td>\n<\/tr>\n
ban <PlayerName><\/code><\/td>\nPermanent ban<\/td>\nRepeat offenders, griefers, or anyone you want gone for good<\/td>\n<\/tr>\n
unban <PlayerName><\/code><\/td>\nRemove a ban<\/td>\nMistaken ban, or someone you’ve decided to give a second chance<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Notes on Banning<\/h3>\n

Romestead’s ban appears to be name-based<\/strong>, not Steam-ID-based, in the current EA build. That means a determined troll can change their display name and rejoin. If someone keeps coming back, combine ban<\/code> with a server password rotation \u2014 change the Password<\/code> in your config and only share the new one with trusted players.<\/p>\n

Communication<\/h2>\n\n\n\n\n\n
Command<\/th>\nWhat it does<\/th>\n<\/tr>\n<\/thead>\n
say <message><\/code><\/td>\nBroadcast a message to every connected player as a server announcement<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Use say<\/code> for: announcing restarts, reminding players about server rules, calling people back to the settlement before nightfall, or just being a benevolent admin.<\/p>\n

Example:<\/strong><\/p>\n

say Server restart in 5 minutes! Save your progress.<\/code><\/pre>\n
World Persistence<\/h2>\n\n\n\n\n\n\n
Command<\/th>\nWhat it does<\/th>\nNotes<\/th>\n<\/tr>\n<\/thead>\n
save<\/code><\/td>\nSave the world to disk immediately<\/td>\nFull save \u2014 takes a moment<\/td>\n<\/tr>\n
quicksave<\/code><\/td>\nSave the world (quick mode)<\/td>\nFaster, less complete checkpoint \u2014 fine for routine snapshots<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Run save<\/code> before any risky operation: applying a patch, letting an unknown player in, testing config changes. Combined with panel backups, this is your defence against losing progress.<\/p>\n
Shutdown<\/h2>\n\n\n\n\n\n\n
Command<\/th>\nWhat it does<\/th>\nWhen to use it<\/th>\n<\/tr>\n<\/thead>\n
stop<\/code><\/td>\nSave the world and shut down gracefully<\/td>\nThe default, almost-always-correct shutdown<\/td>\n<\/tr>\n
quickstop<\/code><\/td>\nShut down without saving<\/strong><\/td>\nOnly when something has corrupted the running state and you want to abandon since-last-save changes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Auto-shutdown:<\/strong> when you click Stop<\/strong> from a managed panel (or send SIGTERM to the dotnet process), the server automatically receives stop<\/code> and waits up to 30 seconds for the save to complete before being force-killed. You don’t normally need to type stop<\/code> yourself.<\/p>\n
Cheat Mode<\/h2>\n
Romestead has a server-wide cheat toggle via config.json<\/code>:<\/p>\n
\"EnableCheats\": true<\/code><\/pre>\n
With this on, cheat commands are available to everyone<\/strong> connected \u2014 not just admins. This is fine for test worlds or sandbox-mode “creative” servers, but you almost certainly do not want it on your main co-op world.<\/p>\n
Beartwigs has not yet shipped a per-Steam-ID admin allowlist or a “give me cheats but not other players” mechanism. If that’s important to you, it’s worth watching the EA roadmap.<\/p>\n
What Romestead Doesn’t Have (Yet)<\/h2>\n
Worth knowing what isn’t in the command set, so you don’t waste time looking:<\/p>\n