Startup parameters · Sven Co-op

Sven Co-op Dedicated Server Install (SteamCMD)

SteamCMD appid 276060

sudo useradd -m -s /bin/bash steam
sudo apt update && sudo apt install -y steamcmd lib32gcc-s1
sudo -u steam -i \
  /usr/games/steamcmd +force_install_dir /opt/gameserver \
  +login anonymous +app_update 276060 validate +quit

https://wiki.svencoop.com/wiki/Running_a_server

Sven Co-op Config file paths

• svencoop/server.cfg
• svencoop/listenserver.cfg
• svencoop/mapvote.cfg
• svencoop/skill.cfg
• svencoop/banned.cfg
• svencoop/listip.cfg
• svencoop/mapcycle.txt
• svencoop/motd.txt
• svencoop/admins.txt
• svencoop/logs/
• svencoop/default_plugins.txt

Server notes

The first old claim to correct: 26900 is neither an HLTV port nor an extra query port. The official port table says verbatim that 26900/UDP is Valve anti-cheat VAC service traffic on the -sport parameter, and that it auto-increments to the next available port when taken, so 26900 is only a start value and the real listening port may be higher. HLTV is the sv_proxies cvar, official default 0. Second: RCON has no port of its own. The official table describes 27015/UDP as game and content transfer traffic plus remote console (RCON) traffic, AMP names that single port Server and RCON Port and sets AdminMethod to GoldSrcRCON, and 27015/TCP is the legacy RCON path marked no longer necessary, so this site emits no rule for it by default. Leaving rcon_password blank disables remote console access, which the official page stresses does not let everyone in. Note that upstream AMP writes rcon_password both into the cfg and onto the command line (+rcon_password); on Linux a command-line secret is readable from the process list by any local user, so keeping it in server.cfg is safer. The launcher is svends_run on Linux or SvenDS.exe on Windows rather than the Source family srcds_run; this is the GoldSrc engine and the dedicated server appid 276060 has oslist windows,linux, so both platforms are native and no Wine is needed. There are two distribution forms: the Steam tool (launchers svends.exe / svends_i686) and the standalone SteamCMD application (launchers SvenDS.exe / svends_run), which the official page presents in two columns with different use cases. All config files live under the svencoop folder, and server.cfg is only read if declared on the command line with +servercfgfile - merely placing the file in the folder is not enough. If you change bannedcfgfile or listipcfgfile you must also change the matching exec line in server.cfg, because the official page says they should match; otherwise the ban list silently fails to load. Multiple instances need no second installation: the official profiling layout is svencoop/servers/<profile>/, the example ports are 27015 / 27025 / 27035 / 27045 (a step of 10), only .cfg files can be shared, and configurations must stay within the game folder. The official page marks five cvars as currently obsolete in Sven Co-op (sv_spectator_password, allow_spectators, sv_alltalk, sv_spectalk, mp_fraglimit) while upstream panels still expose them, so changing those keys has no expected effect. This game has no Steam Workshop (official wording: planned for the future, not currently a high priority); custom content is served over HTTP via sv_downloadurl and sv_allowdownload, with rates controlled by sv_maxrate, sv_minrate and sv_lan_rate. There is also one outbound requirement: HTTPS (TCP 443) to gameinfo.svencoop.com must be permitted. The official Console/Commands page lists 284 command names but its Source, Category, Cheat and Description columns are empty, so this site registers names only and writes no descriptions; the official page also says the only built-in admin functionality currently is using cheat commands, with anything more coming from AngelScript plugins listed in default_plugins.txt. On querying: node-gamedig has no entry for this game as of this round, so third-party query tools built on it may find nothing, which says nothing about server health.