How to Install Mods on a Brickadia Server (Omegga Plugins Guide)

To install “mods” on a Brickadia dedicated server, install the Omegga server wrapper and then add Omegga plugins. The documented setup is: install the Brickadia server files, register a hosting token, expose the server’s UDP port, install Omegga on Linux, WSL, or a container, and install each plugin with the Omegga command line or console. Brickadia’s documented server architecture does not describe a separate official mod-folder installer; Omegga plugins are the practical way to add commands, brick and region tools, wire reactions, environment changes, roles, and other server behavior.

What does “mod” mean on a Brickadia server?

In Brickadia server discussions, “mod” generally means an Omegga plugin. Omegga is a community wrapper around the Brickadia server console. Its plugins can listen for chat and server events, add commands, react to in-game wires, manipulate bricks and regions, alter the environment, manage roles, and implement other server-side behavior.

The Omegga project describes itself as software that “wraps Brickadia’s server console to provide interactivity and utility via plugins along with a web interface for managing your server.” A plugin runs on the server; players do not install the same files in their own Brickadia client. Because the available documentation describes a server-plus-Omegga architecture rather than an official mod directory, treat “install Brickadia mods” as “install Omegga plugins.”

What do I need before installing a plugin?

Prepare the dedicated server, its token, network access, and an environment where Omegga is supported. Omegga is not supported as a direct native Windows installation, so a Windows host needs WSL or a container for Omegga even though the Brickadia server itself can run on Windows.

• A host machine: Brickadia’s manual supports Windows and Linux. You can run the server at home, on a virtual private server, or on bare metal.
• Dedicated-server files: Steam or anonymous SteamCMD can provide the files. The community server guide identifies app ID 3017590.
• A hosting token: Pass it as -token=yourtokenhere on the first launch so the server can register. After successful registration, later launches can omit the token.
• Network access: The default server port is UDP 7777. Forward it on a home router and allow it through the host firewall when players outside the machine or local network must connect.
• Omegga’s runtime: Install it on Linux, WSL, a supported container, or a compatible game-server panel. Do not install or run Omegga as root.
• Plugin documentation: Read the plugin’s README before installation; some plugins require configuration, dependencies, or a setup command.

Windows administrators should distinguish the two programs: the Brickadia dedicated server can be installed through Windows tools, while Omegga should run inside WSL or a container. A December 2025 community Windows guide suggests 8 GB of RAM for a server and 16 GB when the same computer also runs the game; those are community recommendations, not published official minimum requirements.

How do I install the Brickadia dedicated server?

Install the separate dedicated-server tool, launch it once with your hosting token, and make the server reachable on UDP 7777. The exact menus differ between Steam and SteamCMD, but the server files and launch arguments are the same concepts.

Option 1: Install through Steam on Windows

1. Open Steam and search your library or the tools section for the separate Brickadia Server application.
2. Install that server tool rather than the normal game client.
3. Open its launch options and add -token=yourtokenhere for the first run.
4. Start the server and wait for the token registration to complete. Keep the console open long enough to see that the server initializes without an authentication error.
5. After registration succeeds, remove the token argument from routine launches if the server has stored it successfully.

Option 2: Install with SteamCMD

Use SteamCMD when you want a scriptable Linux or Windows installation. Install the dedicated-server app using app ID 3017590, then launch the resulting server executable with the same token argument on its first run. Keep the install directory and the Saved directory backed up separately so a server-file update does not erase worlds or configuration.

Set the port and firewall

Brickadia uses UDP 7777 by default. Forward that UDP port from your router to the server’s local address and create an inbound firewall rule for it. If another service already uses 7777, choose a different value with the server’s -port argument and forward that replacement port instead. Players must use the changed port when connecting manually.

How do I install Omegga?

Install Omegga from a non-root Linux, WSL, or container shell, create a server directory, and start Omegga there. The project provides this Linux-style installer:

curl -fsSL https://omegga.brickadia.dev/install.sh | bash

The installer places the Omegga command on the supported system. If you prefer a manual setup, install Node.js and npm first, then install Omegga according to its project instructions. Do not use sudo to run the Omegga process; running as root can create ownership problems in the server and plugin directories.

1. Open your Linux, WSL, or container shell as the ordinary account that will own the server files.
2. Run the installer command above, or complete the project’s Node and npm manual installation path.
3. Create and enter a dedicated Omegga server directory:

mkdir myServer && cd myServer
omegga

On its first start, Omegga creates the directory structure it needs, including a plugins folder. Point Omegga at the Brickadia server installation when prompted or when configuring the server panel you use. Start the Brickadia server before, or in the order required by your Omegga setup, so Omegga can connect to the server console rather than an absent process.

How do I install an Omegga plugin?

The recommended method is Omegga’s installer, because it can run a plugin’s setup script when the author provides one. You can run the command from the Omegga server directory or issue the equivalent command inside the Omegga console.

Install from the Omegga command line

omegga install https://github.com/user/repo

Omegga also documents a GitHub shorthand:

omegga install gh:user/repo

Replace the repository path in these examples with the plugin repository you intend to use. Check that repository’s README for supported Brickadia or Omegga versions, required settings, permissions, and any external dependency before starting a public server.

Install from the Omegga console

When Omegga is running, enter the same operation through its console:

/plugin install gh:user/repo

The console method is useful when you administer the server remotely through Omegga’s web interface or an attached terminal. Watch the startup output for a successful download, extraction, and plugin load. A setup script may ask for configuration values or create a data file; complete those prompts before testing the plugin in-game.

Manual installation from the plugins directory

Manual cloning is a fallback when the plugin author’s instructions require it:

cd plugins
git clone https://github.com/user/repo

Use the repository’s own README for any post-install step, configuration file, dependency, or required folder name. Restart Omegga after a manual clone if the plugin does not appear in the current process’s plugin list.

How do I update or remove a plugin safely?

Use Omegga’s update command for routine maintenance, and remove a plugin only after checking its cleanup notes. Omegga protects local work by skipping plugins whose Git state indicates that an automatic update could overwrite changes.

Update every plugin or selected plugins

omegga update

To update only selected plugins, provide their names to the update command as described by your Omegga version. Omegga skips a plugin when it has uncommitted changes, is checked out to a branch other than main or master, or contains local commits ahead of the remote repository. Resolve or intentionally preserve those local changes before attempting an update.

Remove a plugin

Stop Omegga if the plugin is actively running, check its README for data-cleanup instructions, and then delete that plugin’s folder under plugins/. Removing the folder may not remove settings or world changes that the plugin already created, so keep a backup and follow the author’s cleanup procedure. Start Omegga again and confirm that the plugin no longer appears in its startup output or web interface.

How can I verify that the plugin works?

Verify the server connection first, then Omegga loading, and only then the plugin’s feature. Testing in a private world prevents a broken command or configuration from affecting public players.

1. Confirm token registration: Start the Brickadia dedicated server and check its console for a successful token-accepted startup rather than an authentication failure.
2. Confirm Omegga loading: Start Omegga and look for the plugin name in its startup output or web interface. A missing name usually indicates a repository, folder, dependency, or configuration problem.
3. Connect locally or remotely: In Brickadia, open Join Game → Manual Connect. Use 127.0.0.1 when the game and server run on the same computer; use the server’s IP address when they run on different machines. Include a non-default port if you changed it.
4. Exercise one documented feature: Enter the plugin’s command, trigger its supported wire or event, or inspect the behavior it claims to add. Use a test world and a non-administrator account when permissions are part of the plugin.
5. Check the logs after the test: A stack trace, permission denial, missing dependency, or configuration parse error identifies the next fix more reliably than a silent in-game failure.

How do I save worlds and protect configuration?

Use the Brickadia server console to create named saves, and back up both world data and Omegga configuration before changing plugins.

BR.World.SaveAs MyWorld
BR.World.Load "MyWorld"
Server.Status

BR.World.SaveAs creates a named world save. Use BR.World.Load after a restart to load that save, and use Server.Status to inspect the running server. The community FAQ places Linux saved data under ~/.config/Epic/Brickadia/ and Windows configuration under the local Brickadia Saved directory.

If multiple servers share one host, isolate their data with the server’s -UserDir=PathToSavedDir argument. Give each instance a different Saved-directory path, port, and Omegga server directory. Back up those paths before updating the dedicated server, changing a plugin that edits bricks, or experimenting with permissions.

What changes when the server runs on Windows?

Windows can host the Brickadia dedicated server, but Omegga itself should run through WSL or a container rather than as a direct Windows installation. This split setup requires you to make the Brickadia executable and its data paths accessible from the Linux environment used by Omegga.

• Install the Steam Brickadia Server tool and add -token=... in its launch options for the initial registration.
• Configure server information through the in-game or server administration menu described by the Windows guide.
• Forward UDP 7777 (or your selected replacement port) on the Windows firewall and home router.
• Install Omegga in WSL or a container, not directly in the Windows shell, because direct Windows installation is unsupported by Omegga’s installation documentation.
• Keep Windows server files, WSL/container files, plugin repositories, and Saved data in known locations so backups and permission checks are straightforward.

Should I self-host, use a VPS, or choose managed hosting?

The right option depends on whether you value direct control or reduced administration. A home server gives you the most control over files and firewall rules but exposes your network and depends on your upload bandwidth and uptime.

Hosting approach	Strengths	Trade-offs to check
Home self-hosting	Direct access to server files, firewall, backups, launch arguments, and plugin repositories; no separate hosting bill.	Router port forwarding, changing home IP addresses, power or ISP outages, and responsibility for security and updates.
VPS or bare metal	Moves the server away from your home network; suitable when you want an always-on machine and shell access.	Recurring infrastructure cost and responsibility for operating-system updates, backups, firewall rules, and Omegga maintenance.
Managed game hosting	Usually offers a control panel, FTP access, custom launch parameters, and advertised Brickadia plugin or mod-management features.	Verify Linux or container support for Omegga, shell access, backup policy, player capacity, plugin compatibility, network limits, and the recurring price before committing.

Compare providers on operating-system and shell access, who performs updates and backups, network exposure, compatibility with the plugins you need, expected player capacity, and recurring cost. A control panel does not automatically guarantee that every Omegga plugin or setup script will work; confirm that the host permits the required files, processes, and ports.

Why is my plugin not loading?

Most failures occur before the plugin reaches the game: an unsupported Omegga environment, an incorrect repository path, a missing dependency, or a configuration error. Use the symptom that matches your installation.

Omegga will not start

• Confirm you are running Omegga in Linux, WSL, a supported container, or a compatible panel rather than directly on Windows.
• Check that Node and npm are installed when using the manual installation path.
• Run the process as the normal server user, not root, and fix ownership of directories created by an earlier root launch.
• Verify that the Brickadia server executable path and Saved directory are accessible from the environment running Omegga.

The plugin does not appear after installation

• Check the repository path and whether the clone created an extra nested folder under plugins.
• Read the plugin README for a required branch, dependency, setup script, or configuration file.
• Restart Omegga after a manual clone and inspect startup output for a load error.
• Make sure the plugin targets the Omegga and Brickadia versions you are running; do not assume an old repository remains compatible.

The command works for an administrator but not players

Inspect the plugin’s role or permission configuration. Test with the intended player role in a private world, then grant only the permissions required for the feature. If the plugin manages roles itself, follow its documented setup instead of editing unrelated server files.

Players cannot connect

• Use 127.0.0.1 only for a game running on the same machine; remote players need the server machine’s reachable IP address.
• Confirm UDP 7777 is forwarded to the correct local address and allowed through the firewall.
• If you changed -port, forward and enter that new port consistently.
• Check Server.Status and the server console before troubleshooting the plugin itself.

What is the safest installation workflow for a public server?

Build and test in a separate Omegga directory or private instance, then promote the known-good configuration to the public server. Keep a dated backup before every plugin update and before installing plugins that alter bricks, regions, roles, or world state.

1. Install and register the dedicated server without plugins.
2. Confirm local and remote connectivity on the chosen UDP port.
3. Install Omegga in a non-root Linux, WSL, or container environment.
4. Install one plugin at a time through omegga install so a failure has a clear cause.
5. Read and apply its configuration and permission instructions.
6. Save a test world, exercise the feature, and inspect logs.
7. Back up the Saved directory and Omegga directory before enabling it for public players.
8. Schedule updates, review skipped Git repositories manually, and remove abandoned plugins by following their cleanup instructions.

Frequently Asked Questions

Do players need to install Omegga or the plugin to join my server?

No. Omegga and its plugins run on the server host. Players connect with the regular Brickadia client; they only need the server address and port, plus any access credentials or role requirements your server applies.

Can I run several Brickadia servers on one computer?

Yes, but give each instance its own port, Omegga server directory, and Saved-data location. The server’s -UserDir=PathToSavedDir argument is designed to relocate the Saved directory so worlds and configuration do not overlap.

What should I do before updating a plugin that changes bricks or worlds?

Create a named save with BR.World.SaveAs, stop or isolate the public instance, and copy the Saved and Omegga directories to a backup location. Test the update in a private instance first, because a plugin can leave persistent world changes even after its folder is removed.

Why does Omegga skip my plugin during an update?

Omegga avoids automatic updates when the plugin has uncommitted changes, is on a branch other than main or master, or has local commits ahead of the remote. Review the repository state and decide whether to commit, stash, switch branches, or update manually.