Empyrion Workshop Scenarios and Mods on a Dedicated Server
Empyrion uses “scenario” for a large package of world content and rules, while smaller changes may be distributed as configuration or additional content. Treat the scenario as part of the save contract, not as a cosmetic client add-on.
What belongs where
| Content | Server needs | Players need |
|---|---|---|
| Scenario files | Complete folder under the server content tree and a YAML reference. | Matching game build and scenario availability. |
| Scenario configuration | Active scenario config for the server/save. | Matching scenario release. |
| Optional client mod | Only if it changes server-visible behavior. | Usually the same version and loadout. |
Safe modded-server routine
- Back up the named save and scenario before changing the stack.
- Add one scenario or mod at a time.
- Start with no players and read the log for missing assets.
- Test a clean client before asking the whole group to update.
- Keep the previous files until the new save has been verified.
Reforged Eden 2 is the common example, but the same rule applies to every scenario: its folder identity and version must remain compatible with the galaxy that uses it.
See the custom scenario upload guide and managed Empyrion hosting for the safer update path.