Before you start
You need service administration rights, the actual game build, allocated network settings and a copy of existing files. Paths are relative to the server folder actually in use. Keep the original backup intact while testing.
Identify the world and preserve a recovery copy
Record the build from logs and identify the Servers folder belonging to the instance. Back up both the world and configuration. SDG explains that Save writes world data and Shutdown saves before closing normally; neither should be confused with an independent recoverable copy. Stop writes before copying files and keep the original outside the server. Confirm that the copied files are readable before editing the working installation.
Set Vanilla, PvP or PvE rules in Commands.dat
Server/Commands.dat accepts basic settings with one command per line. Map PEI selects that official map, while PVE enables its cooperative rule setting. Choose a name, an optional joining password and a player limit appropriate to the project. That limit is not a guaranteed hosting capacity. Keep administrator permissions separate from ordinary players rather than granting extra privileges to solve a connection problem.
Check Config.txt before following an older tutorial
Current documentation uses Config.txt for many advanced settings. Servers created before 3.25.8.0 used Config.json for several difficulty levels. Conversion produces difficulty-specific files, such as Config_NormalDifficulty.txt, containing changed values. A launch option can select another configuration file. Establish which difficulty and file your actual installation loads. Renaming a JSON file to TXT is not a conversion, and replacing every setting with an online sample can discard working rules.
Add Workshop content and check dependencies
Open the map or mod’s Steam Workshop page and identify its numeric file ID in the URL. Add it to the existing WorkshopDownloadConfig.json File_IDs list while preserving valid JSON. Review author-listed dependencies, availability and game-version compatibility. Players download configured content when joining. Start with one addition, check map loading and test a player connection. Server extensions and content downloaded by clients have different roles, so a server plugin should not be treated automatically as a Workshop item.
Keep the GSLT private and distinguish listing from joining
A GSLT registers an Internet server. Follow SDG’s official Game Server Login Token link and enter your own value in the protected setting used by your build. A simple server can be reached through Steam invitations or a server code without being publicly listed. Test joining and public listing separately. For managed hosting, use the assigned address and ports rather than changing the host firewall or guessing network settings.
Validate OpenMod or RocketMod with their own prerequisites
Consult the maintainer’s supported versions and dependencies before adding either framework. Coexistence may require the documented integration and does not make every plugin compatible. Preserve working files, check permissions and add one component at a time. Validate joining, the world and persistence after a normal restart. Observe CPU and memory during representative play: maps, vehicles and constructions all affect demand, and memory alone cannot guarantee a player count.
For your situation
| Situation | Next check |
|---|---|
| The Vanilla world works | Add one map or mod at a time with its dependencies. |
| Joining works but public listing does not | Check GSLT and listing conditions separately from server uptime. |
| An update breaks an extension | Compare supported versions and recover a coherent saved configuration before retesting. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.