Skip to content
Back to Homepage

How to install Mods on your Avorion Server

Avorion servers can automatically download and install mods directly from the Steam Workshop.

This is the recommended method by the developers. The server and clients automatically install and update Workshop mods. Mods not on the Steam Workshop can be used but must be installed and updated manually.

Each Steam Workshop mod has a numeric ID in its URL.

For example, in https://steamcommunity.com/sharedfiles/filedetails/?id=2884880231, the Workshop ID is 2884880231.

Subscribe to the mods in Steam on your client before adding them to the server.

Installing Steam Workshop mods on your Avorion server is done by creating and editing a file called modconfig.lua in your galaxy. This file must be created or uploaded to your server’s Avorion folder (or your custom galaxy name folder). If you have not started the server at least once, you will not see the Avorion folder yet.

In modconfig.lua, list the Workshop ID for each mod. The server downloads and updates mods from that list.

Mods are downloaded to a workshop folder inside your galaxy directory, under content/445220/. 445220 is Avorion’s Steam application ID.

  1. Open the AleForge Panel and go to File Manager
  2. Open your galaxy folder at galaxy/Avorion (or your custom galaxy name)
  3. Click New File and paste the template below
modLocation = ""
forceEnabling = false
mods =
{
{workshopid = ""},
}
allowed =
{
}

4. Replace the empty workshopid entries with your mod IDs:

mods =
{
{workshopid = "2884880231"},
{workshopid = "2854314758"},
{workshopid = "2888955026"}
}

5. Make sure the last workshopid line does not have a trailing comma. 6. Save the file as modconfig.lua 7. Open Console and restart the server to install your mods

When you join the server, Avorion may prompt you to download the mods added on the server. Accept the prompt so your client matches the server.

Check the server Console or event log after restart to confirm mods are downloading without errors.

  • Confirm each Workshop ID is correct and the mod supports dedicated servers
  • Make sure modconfig.lua is in the active galaxy folder, not the server root
  • Restart the server after editing modconfig.lua
  • Verify the client downloaded the same mods when joining
  • Remove trailing commas from the last entry in the mods table

If you still cannot connect after adding mods, see Avorion Server Not Showing or Unable to Connect.