Brickadia
on your own machine, for you and your players
The multiplayer brick building sandbox. Installs the dedicated server with SteamCMD and keeps it updated; it needs a server hosting token from a Brickadia account.
$12 a month per machine, with as many servers as it can run. Already on Raptor? It's in your team's Eggs, as steam/brickadia.
What Raptor does for it
- Backups
- Incremental and encrypted on your machine, every day by default. Restore one file or the whole server.
- Runs on
- x86 machines, on Raptor's SteamCMD image.
- Every server
- A live console, a file manager with a trash, schedules, crash restarts, alerts, and SFTP. It keeps running if Raptor goes down.
Settings you can change
From the server's Startup tab, without touching a file.
- Server hosting token
- The token from your Brickadia account's server hosting page, which the server signs in with.
- World
- The world the server loads and saves to, created when there's none by that name.Default
world - Server name
- The name players see in the server list.Default
A Brickadia server - Server password
- The password players join with, or empty for none.
- Public
- List the server in the public server list.Default
True - Auto update
- Update the game from Steam every time the server starts.
- Validate files
- Check every game file against Steam when installing or updating, which repairs damaged files but takes longer.
- Beta branch
- The Steam beta branch to install, or empty for the normal release. Reinstall after changing it.
- Beta password
- The password of a private beta branch, if it has one.
From a bare machine
Link your machine
One command on any Debian or Ubuntu box, at home or rented.
Pick Brickadia
Raptor installs it and starts it, on images it keeps updated.
Invite your players
They connect straight to your machine, at the address it comes with.
Made by Raptor and MIT-licensed. Based on the Brickadia egg in https://github.com/pterodactyl/game-eggs (MIT) Icon: Brickadia's icon, from Steam (Brickadia) The egg's source.