Empyrion: Scenarios & Server Mods

← All guides · GAME GUIDE

Empyrion scenarios and executable server mods are different packages. Open Server Options → Mod & Plugin Manager and select the appropriate add-on system. Back up and stop before making changes.

Import a scenario

1. Obtain a complete server scenario from its author or Steam Workshop. A blueprint or collection is not automatically a scenario.
2. Click Import ZIP / folder, then choose the complete ZIP or extracted scenario folder.
3. For a Workshop copy, choose the individual scenario inside your Steam library's steamapps/workshop/content/383120 folder after Steam finishes downloading it.
4. Let Synix inspect the package. A recognized scenario includes its scenario configuration and assets.
5. Give the installed scenario a recognizable folder name, not only the numeric Workshop ID. Keep that name for updates.
6. Review the destination under Content/Scenarios, then confirm.

Import copies the scenario. It does not activate it, start the game, replace an existing world, or prove that the scenario supports your game version.

Choose the scenario and a save

Use Choose Scenario, select an installed scenario, and review the separate save name.

Setting	Meaning
GameConfig.CustomScenario	Installed scenario folder
GameConfig.GameName	Saved-world/session name

Changing to a different scenario requires a new, unused save name. Synix suggests one and preserves existing saves. It backs up dedicated.yaml before changing these fields and updates the server entry without resetting unrelated seed/password settings.

Start manually, check the game log, and test a client. Follow any additional scenario-author configuration or fresh-world requirements.

Import server-code mods

Choose the Empyrion server-mod system and import a complete compiled ZIP or folder. Include the DLLs, dependencies, assets, and _Info.yaml when supplied.

The supported destination is Content/Mods. The game loads the mod's code on startup. A source-code repository or standalone executable installer is not a ready server-mod package.

Synix does not automatically install an arbitrary loader or enable a disabled mod. Follow the author's server, loader, configuration, and client requirements.

Update a scenario or mod

Steam updates its Workshop copy, not the server copy previously imported by Synix.

Stop and back up, then import the updated package with the same installed folder name. Review replacements and check whether the author requires a new save. Importing an update is not a clean reinstall: files absent from the new package are not automatically removed.

Recovery

Roll Back Import reverses the recorded operation, which can include several packages. Replaced files have preserved originals; introduced files can be removed. Later external edits are not silently overwritten.

The active scenario and assets needed by existing saves are protected from removal. A recorded scenario update can still be rolled back to its previous files; this is different from removing the scenario entirely.

“Installed (not re-verified)” means the import was recorded, not that all files were rescanned just now. Keep independent full backups of worlds and configuration.

Related: Mods & Plugins · Configuration Editor and YAML · Backups