Server administration and Workshop data
Guides
Clear, practical guides for launching servers, managing mods, fixing config problems, and building tools on top of reliable Workshop metadata.
12 guides · free tools
Server administration
GuideDeploy your first serverInstall the dedicated server, create config.json, open ports, launch it, and verify players can join.
Guideconfig.json explainedWhat every major field does: ports, A2S, RCON, game settings, scenarioId, gameProperties, and mods.
GuideHow to add modsFind the mod ID, write the game.mods entry, handle dependencies, and verify the server loads it.
GuideServer config exampleA working config.json shape with ports, scenarioId, game settings, and a mods array.
GuideFind a mod IDCopy Workshop IDs from the mod browser, official URLs, or API responses.
Guideconfig.json troubleshootingTrailing commas, smart quotes, misplaced mods arrays, bad ports, and scenario mistakes.
GuideRunning server modsHow mod downloads work, what dependencies mean, version pinning, and staying stable.
GuideMod dependenciesFind required mods, resolve them for the whole mod set, and avoid duplicate entries.
GuideScenarios and scenario IDsThe scenarioId format, modded scenarios, discovering IDs, and setting game.scenarioId.
GuideServer mod orderOrganize the mods array for review, dependency checks, and clean exports.
API and development
Do it with the tools instead
Most of what these guides describe by hand can be done in the browser: search mods in the mod browser, build a config in the config generator, manage the mods array in the mod manager, and check the result with the config validator.
Developer reference
Building on the data itself? Start with the API documentation overview, then choose the V2 reference for typed mod data or the V1 reference for legacy response shapes. The quickstart gets a first request working in minutes.