Empyrion's big community projects are scenarios rather than mods. A scenario replaces the playfields, blocks and progression, and it has to be installed on the server and on every player's PC.
1. Get the scenario
- Subscribe to the scenario in the Steam Workshop on your own PC and let it download.
- Open your local Empyrion folder and go to
Content/Scenarios. - The scenario is a folder there, named after the scenario.
2. Upload it to the server
- Stop the server in the Game Panel.
- Open the Files tab and go to
Content/Scenarioson the server. - Upload the whole scenario folder, keeping its name exactly as it is. Use SFTP, since scenarios are large.
3. Point the server at it
- Open
dedicated.yaml. - Under
GameConfig, setCustomScenarioto the scenario folder name. - Set
GameNameto a new value. A scenario change needs a new save, because the playfields no longer match the old galaxy. - Save and start the server. The first start builds the new galaxy and takes a while.
4. Get your players ready
- Players subscribe to the same scenario in the Steam Workshop.
- The version must match. After the scenario author publishes an update, the server files need updating too, or players are refused.
- Tell your group which scenario you run and link the workshop page.
5. Keeping a scenario updated
- Take a backup of your save first.
- Stop the server, replace the scenario folder with the new version, and start it.
- Read the console. Scenario errors are reported by playfield name, which tells you which part failed.
- Some scenario updates require a new galaxy. The author's notes will say so, and ignoring that is the usual cause of a broken save.
Open a ticket from Support in the Client Area with the console output if the server will not start after a scenario change.





