Brickadia administration depends on where you enter a command. The dedicated-server terminal accepts native commands such as BR.World.Load and Server.Status; in-game chat uses slash commands such as /Kick and /GrantRole; and many hosted panels require the br.chat.command prefix before a slash command. Your role determines which commands are available. Before changing a map, clearing entities, or moderating a player, confirm the target, check the installed build’s /Help output or auto-completion, and save the world.
What are Brickadia server admin commands?
Brickadia commands are administrative instructions for managing players, roles, worlds, maps, bricks, entities, and server status. They are not entered identically in every interface. A command copied from a dedicated-server guide may fail in a hosted console if it needs a prefix, while a slash command pasted into the native terminal may be treated as unknown.
The practical command list maintained by the Brickadia Community Wiki is not an official exhaustive reference. Brickadia’s permission and command systems have changed between releases, including Alpha 5, so treat examples below as a working reference and verify syntax on the server you actually run. Use /Help, the in-game console’s auto-completion, or a harmless status command before issuing a mutating command.
Where can I run a Brickadia command?
Choose the execution context first. The same operation can require a different prefix, and the visible command history and permission checks differ by interface.
| Context | How to enter commands | Typical syntax | Best use |
|---|---|---|---|
| Dedicated-server terminal | Type directly in the terminal window running the server. | BR.World.SaveServer.Status |
Server-wide operations, world loading and saving, status checks, and initial role setup. |
| Hosted server console | Use the provider’s console. Most chat commands need br.chat.command before the slash command. |
br.chat.command /Helpbr.chat.command /Kick "Player Name" |
Remote administration when the host panel exposes the Brickadia console. |
| In-game chat | Connect to the server, open chat, and type a slash command. | /ListPlayers/GrantRole Admin PlayerName |
Quick player and moderation actions while connected, subject to your role. |
| In-game client console | Press the backtick key to open the console and use command auto-completion. | Begin typing a command and select a completion. | Discovering commands and checking the syntax supported by the installed build. |
Hosted panels can expose additional logging or history, but the command itself still runs with the permissions assigned to the caller. Native terminal commands and chat commands are related, not interchangeable: BR.World.Save is a native console command, whereas /Kick is a chat command.
What do I need before administering a dedicated server?
You need the server files, a registered hosting token, access to the process or host console, and a clear understanding of where the server stores its data. Steam or SteamCMD supplies the dedicated-server files. The current default network port is UDP 7777; if you change it, players must use the resulting address and port.
- Hosting token: the server requires one during first registration.
- Data location: the
-UserDirlaunch option can relocate saved data, so do not assume the default directory when searching for worlds or configuration. - Windows visibility: if a Windows launch has no visible console, start
BrickadiaServer-Win64-Shipping.exewith the-logflag. - Version check: record the installed build and use its own help output because permissions and command behavior have changed across releases.
On Linux, the usual configuration path is ~/.config/Epic/Brickadia/Saved/Config/LinuxServer/GameUserSettings.ini. On Windows it is C:Users<yourusername>AppDataLocalBrickadiaSavedConfigWindowsServerGameUserSettings.ini. A custom -UserDir changes where saved data is written, so use the effective launch path when locating files.
How do I give someone admin or remove a role?
Grant a role only to a trusted account, and use the form that matches your console. The role controls which commands the player can run; a syntactically correct command still returns a permission error if the caller lacks the required role.
Dedicated-server terminal
Enter the native terminal form, replacing the player name with the account you intend to authorize:
Chat.Command /GrantRole Admin PlayerName
The community dedicated-server reference shows the same command with a placeholder in brackets. Do not type the brackets unless they are genuinely part of the player’s name.
Hosted server console
Hosted consoles generally route chat commands through the br.chat.command wrapper:
br.chat.command /GrantRole Admin PlayerName
If the account name contains spaces, quote it: br.chat.command /GrantRole Admin "Player Name".
In-game chat
When connected as an authorized operator, use:
/GrantRole Admin PlayerName
To remove a role, use the corresponding revoke command:
/RevokeRole Admin PlayerName
Check available roles with /ListRoles. If an expected role is absent or a command is hidden, inspect the server’s role configuration rather than repeatedly changing the command spelling.
How do I discover the commands supported by my server?
Start with read-only checks. They establish whether you are in the correct context before you run a command that changes players or persistent world data.
- In chat or a compatible hosted console, run
/Help. To request details for one command, run/Help CommandName. - From the dedicated terminal, run
Server.Statusto confirm that the process is responding. - Use
/ListPlayersand/PlayerCountto verify that the session and player list are visible. - Press the backtick key in the client console and type the first characters of a command. Select an auto-completion entry instead of relying on an older wiki example.
- Record the exact output and the interface used. A command that works in chat may require the hosted-console prefix, while a native command may be unavailable in chat.
The community FAQ states that most client commands are also available on the server console, but availability remains role-dependent and version-dependent. Treat auto-completion and current /Help output as the authority for your installation.
Which commands manage players and moderation?
Moderation commands affect connected users immediately. Confirm the target’s exact name, duration, and reason before pressing Enter; quote any argument containing spaces.
| Purpose | Chat command | Notes |
|---|---|---|
| List players | /ListPlayers |
Use first to verify the exact player name. |
| Kick | /Kick Player Reason |
Disconnects a player; the reason is optional. Quote a multi-word name or reason. |
| Ban | /Ban Player TimeInMinutes Reason |
Applies a duration in minutes and an optional reason. Check the target and duration before execution. |
| Unban | /Unban Player |
Removes a ban for the specified player. |
| Grant a role | /GrantRole Role Player |
Requires permission to change roles. |
| Revoke a role | /RevokeRole Role Player |
Removes the named role from the player. |
For a hosted console, prepend br.chat.command to each chat command. For example, a temporary ban entered there would look like br.chat.command /Ban "Player Name" 30 "Repeated spam". The command guide does not establish a universal case-sensitivity rule, so use the spelling shown by /Help and auto-completion.
How do I teleport players or clear bricks and entities?
Movement commands are usually reversible, but clearing commands can destroy placed content or remove entities for everyone. Save the world before broad cleanup.
Teleportation
/TPteleports yourself to the location you are aiming at./TP DestinationPlayerteleports yourself to another player./TP TargetPlayer DestinationPlayerteleports one player to another.
Use /ListPlayers first when names are similar. Quote names containing spaces.
Brick and entity removal
/ClearBricks Playerclears the specified player’s bricks and entities; without a player argument, the command can target your own content according to the server’s current help text./ClearAllBricksclears all placeable bricks and entities. The provider guide labels this command “Use with caution!”/ClearAllEntitiesand/ClearAllLooseEntities, along with player- or distance-scoped variants, affect broader entity sets. Run/Help ClearAllEntitiesor the corresponding help entry before use.
These operations may affect the entire session or persistent save, not just the operator. A save made immediately before cleanup gives you a recovery point; it does not make an already executed clear command automatically reversible.
How do I save, load, or change a Brickadia world?
Use native world commands in the dedicated-server terminal, and save before switching levels or performing destructive edits.
Save the current world
BR.World.Save writes the current world under its existing name.
Save a separate copy
BR.World.SaveAs SaveName creates a save with a new name. The provider guide documents the native console spelling as br.world.saveas Name; unlike chat commands, it does not use the br.chat.command prefix.
Load a saved world
BR.World.Load "World Name" loads a saved world by name. The quotation marks are required when the name contains spaces.
For a custom .brdb world, place the file in the server’s Saved/Worlds directory and omit the extension in the load command. A file named office world.brdb is loaded with:
BR.World.Load "office world"
If a restart produces an empty or unexpected world, run BR.World.Load "WorldName" and verify that the matching file exists in the effective worlds directory, especially when -UserDir is in use.
What is the safest way to change the map?
Brickadia exposes two level-travel forms with different effects on connected players.
| Command | Effect | Trade-off |
|---|---|---|
servertravel Studio |
Switches the server level while clients remain connected. | The FAQ warns that connected clients can sometimes crash. |
travel Studio |
Disconnects all clients before changing the level. | Avoids the stated client-crash behavior, but everyone must reconnect. |
- Warn players and decide whether a disconnect is acceptable.
- Run
BR.World.SaveorBR.World.SaveAs BackupName. - Use
travel LevelNamewhen a clean disconnect is preferable; useservertravel LevelNameonly when keeping players connected is more important than the reported crash risk. - After the transition, check
Server.Statusand/ListPlayers.
The example level Studio is the documented syntax; use the level name supported by your installed server and confirm it with /Help if the build reports an error.
Why does Brickadia say I do not have permission?
A permission error usually means the command is valid but the caller’s role does not include that command. It can also occur when you are testing from in-game chat with a role that is allowed to play but not administer.
- Run
/ListRolesto see role names available on the server. - Have an authorized operator grant the needed role with the context-specific
GrantRoleform. - Check the role’s command permissions in the server configuration or management layer.
- Reconnect if the server only applies role changes to a new session, then test with
/Helpor/ListPlayers. - Do not grant a broad administrator role merely to bypass one failed command; use the narrowest role that includes the required action.
Permissions can change between server versions. If a command worked before an update, compare the current role configuration and installed build rather than assuming the syntax changed.
How do I fix “unknown command” or no output?
First determine whether you entered a native command or a chat command in the wrong place.
| Symptom | Likely cause | Correction |
|---|---|---|
| Unknown command in a hosted console | A slash command was entered without the panel’s wrapper. | Try br.chat.command /Help or the panel’s documented chat-command format. |
| Unknown command in the dedicated terminal | A chat command was entered where a native command is expected. | Use the native form, such as Server.Status, or route the slash command through Chat.Command as documented for that terminal. |
| No result from a valid-looking command | The command is unavailable to the caller’s role or differs in the installed version. | Run /Help CommandName, inspect auto-completion, and verify permissions. |
| Names or world files with spaces fail | The argument was split into multiple tokens. | Wrap the complete name in quotation marks. |
| World is empty after restart | The saved world was not loaded automatically or the server is using another data directory. | Run BR.World.Load "WorldName" and verify the file under the server’s active Saved/Worlds path. |
| No Windows console appears | The server was launched without a visible log window. | Launch through Steam or add -log to BrickadiaServer-Win64-Shipping.exe. |
| Players crash during a map switch | servertravel can sometimes crash connected clients. |
Use travel if disconnecting everyone is acceptable. |
Should I use Omegga instead of the native console?
Omegga is an optional management layer that wraps the Brickadia server console. Its web interface can handle world management, startup and restart loading, chat, kick and ban history, plugin configuration, and multi-user role-based permissions.
Plugins can add custom commands and automate tasks such as loading or clearing regions, teleporting players, changing the environment, and granting roles. That convenience comes with another configuration surface: you must secure the web interface, understand which users can invoke plugins, and still verify the underlying server version when a command changes.
| Option | Visibility and control | Best fit | Main risk |
|---|---|---|---|
| Native terminal | Direct server output and full process access. | Owners who need low-level control and reliable startup diagnostics. | Easy to affect the whole world; terminal access must be protected. |
| In-game chat or client console | Immediate feedback while connected; limited by the caller’s role. | Moderators handling routine player actions. | Easy to target the wrong player or run a destructive command during play. |
| Hosted panel | Remote console, provider logs, and often easier restart controls. | Administrators who do not manage the operating system directly. | Panel-specific prefixes and permissions can obscure whether a failure is syntax or access. |
| Omegga | Web history, multi-user roles, plugins, and automation. | Communities needing recurring workflows or several staff members. | Plugins and web permissions expand the administrative attack surface. |
What is a safe operating procedure for Brickadia administration?
Use a short preflight routine whenever a command can affect players or persistent data.
- Identify the context and build. Note whether you are in the native terminal, a hosted panel, chat, or the client console, and check the installed version.
- Check access. Confirm that your role includes the command. If another operator is granting access, use the smallest role that solves the task.
- Test harmlessly. Run
/Help,Server.Status,/ListPlayers, or/PlayerCountbefore a mutating command. - Confirm arguments. Match the exact player or world name, quote spaces, and verify ban duration and reason.
- Save first. Use
BR.World.SaveorBR.World.SaveAsbefore map changes, clearing commands, or other world edits. - Warn players. Tell connected users whether they may be kicked, disconnected, or exposed to a level transition.
- Execute once. Avoid repeated submissions when output is delayed; check status before trying again.
- Verify and record. Confirm the resulting player list, status, or world name and keep an operator log with the time, command, target, and outcome.
This process separates a syntax problem from a permission problem and gives you a known save point before a destructive action.
Which command should I use for a common task?
| Task | Native terminal | In-game chat | Hosted console |
|---|---|---|---|
| Check server response | Server.Status |
Use /Help or /PlayerCount |
br.chat.command /PlayerCount |
| See players | Use the server’s current chat-command route | /ListPlayers |
br.chat.command /ListPlayers |
| Grant admin | Chat.Command /GrantRole Admin PlayerName |
/GrantRole Admin PlayerName |
br.chat.command /GrantRole Admin PlayerName |
| Save current world | BR.World.Save |
Use the native console route | Use the panel’s native-console command field |
| Load a world | BR.World.Load "WorldName" |
Use the native console route | Use the panel’s native-console command field |
| Kick a player | Use the chat-command route supported by the terminal | /Kick Player Reason |
br.chat.command /Kick Player Reason |
When a cell says to use the native-console route, do not substitute a slash command blindly. Run the installed server’s help or use the panel’s command-type selector to determine how that interface routes chat commands.
Frequently Asked Questions
Where does Brickadia store a custom world file?
Custom worlds use the server’s Saved/Worlds directory and normally keep the .brdb extension on disk. If the launch uses -UserDir, that directory is relocated, so search under the active user-data path rather than only the default installation folders.
Can I administer a Brickadia server without opening a Windows console window?
Yes. Start the Windows server through Steam or launch BrickadiaServer-Win64-Shipping.exe with -log so output is available in a log window. A hosted console or a management layer can also provide remote output, but its command prefixes may differ.
Why did a map change disconnect or crash players?
travel intentionally disconnects all clients before changing the level. servertravel attempts to keep them connected, but the Brickadia FAQ warns that connected clients can sometimes crash during that transition.
Does Brickadia have an official complete admin-command list?
No complete official list is published in the community FAQ. Use the installed server’s /Help output and client-console auto-completion as the final authority, especially after an update that changes permissions or command behavior.
How can several moderators share administration safely?
Use role-based permissions instead of sharing the owner account. A management layer such as Omegga can provide separate users, command permissions, and history, while the underlying server roles should still be limited to the actions each moderator needs.