Avorion Workshop Mods on a Dedicated Server
Avorion can download Workshop mods for the server and tell clients which Workshop items they need. The control file is modconfig.lua in the galaxy directory.
Keep the mod stack reproducible
| Step | Why |
|---|---|
| Back up the galaxy | A mod update can change scripts or behavior in an existing world. |
| Record Workshop IDs | Names and display pages can change; IDs are the useful record. |
| Test one update | Separates a bad mod from a server or network failure. |
| Check client download | Players need compatible client-side content when the mod requires it. |
Workshop versus local mods
Workshop entries are the easier path because the server can download them. Non-Workshop mods require a stable server path and a deliberate distribution plan. If both a path and Workshop identity are configured, keep their versions aligned.
Mods can disable achievements and can change the behavior of a long-lived galaxy. Treat a mod list as part of the backup, not as disposable decoration.
For rollback, see the galaxy backup guide. Managed Workshop updates are part of Avorion hosting.