User:Nosoop/Guide/Game Server Configuration - Revision history

Nosoop: /* Team Fortress 2 */ Hoist Debian package names for replay_srv to platform-specific

2026-06-12T10:23:14Z

‎Team Fortress 2: Hoist Debian package names for replay_srv to platform-specific

Nosoop: /* Team Fortress 2 */

2026-06-12T10:19:52Z

‎Team Fortress 2

Nosoop: /* General */ Add section on profiling

2023-09-22T03:45:13Z

‎General: Add section on profiling

Nosoop: /* Using Workshop maps */ Add note on +map

2023-07-22T15:24:20Z

‎Using Workshop maps: Add note on +map

Nosoop: /* Using Workshop maps */

2023-07-22T15:22:58Z

‎Using Workshop maps

Nosoop: /* Using Workshop maps */ Next person to suggest subscribing dies

2023-07-22T15:15:26Z

‎Using Workshop maps: Next person to suggest subscribing dies

Nosoop: /* Using Workshop maps */ Convert heading to use note

2023-07-15T05:31:16Z

‎Using Workshop maps: Convert heading to use note

Nosoop: /* Using Workshop maps */ Reword TF2-specific heading

2023-07-15T05:29:35Z

‎Using Workshop maps: Reword TF2-specific heading

Nosoop: /* Using Workshop maps */ Add note that this is TF2-specific

2023-07-15T05:27:44Z

‎Using Workshop maps: Add note that this is TF2-specific

Nosoop: /* Team Fortress 2 */ Add section on using Workshop maps

2023-07-15T05:26:16Z

‎Team Fortress 2: Add section on using Workshop maps

@@ Line 106: / Line 106: @@
 * Fedora: <tt>yum -y install glibc.i686 zlib.i686</tt>
-= Game Specific =
+Addiionally, on Team Fortress 2 you may see the following error:
-== Team Fortress 2 ==
+<pre>FATAL ERROR: Could not load: replay_srv.so</pre>
-The [https://wiki.teamfortress.com/wiki/Dedicated_server_configuration Dedicated server configuration] section on the Team Fortress 2 Official Wiki provides general configuration instructions.  Depending on the platform you're working on, you may also be interested in the sections for [https://wiki.teamfortress.com/wiki/Linux_dedicated_server Linux] and [https://wiki.teamfortress.com/wiki/Windows_dedicated_server Windows].
+The replay library expects <tt>libcurl-gnutls.so.4</tt>.  If you are running a 32-bit Team Fortress 2 instance, install the following package (depending on the specific version of the OS):
-=== FATAL ERROR: Could not load: replay_srv.so ===
+* <tt>libcurl4-gnutls:i386</tt> (on Debian 12 and older)
-The replay library expects <tt>libcurl-gnutls.so.4</tt>.
+= Game Specific =
-If you are running 64-bit Debian or Ubuntu and attempting to run a 32-bit Team Fortress 2 instance, install the following package:
+== Team Fortress 2 ==
-* <tt>libcurl4-gnutls:i386</tt> (on Debian 12 and older)
+The [https://wiki.teamfortress.com/wiki/Dedicated_server_configuration Dedicated server configuration] section on the Team Fortress 2 Official Wiki provides general configuration instructions.  Depending on the platform you're working on, you may also be interested in the sections for [https://wiki.teamfortress.com/wiki/Linux_dedicated_server Linux] and [https://wiki.teamfortress.com/wiki/Windows_dedicated_server Windows].
 === Mann vs. Machine ===

← Older revision		Revision as of 10:19, 12 June 2026
Line 111:		Line 111:

	The [https://wiki.teamfortress.com/wiki/Dedicated_server_configuration Dedicated server configuration] section on the Team Fortress 2 Official Wiki provides general configuration instructions. Depending on the platform you're working on, you may also be interested in the sections for [https://wiki.teamfortress.com/wiki/Linux_dedicated_server Linux] and [https://wiki.teamfortress.com/wiki/Windows_dedicated_server Windows].		The [https://wiki.teamfortress.com/wiki/Dedicated_server_configuration Dedicated server configuration] section on the Team Fortress 2 Official Wiki provides general configuration instructions. Depending on the platform you're working on, you may also be interested in the sections for [https://wiki.teamfortress.com/wiki/Linux_dedicated_server Linux] and [https://wiki.teamfortress.com/wiki/Windows_dedicated_server Windows].
		+
		+	=== FATAL ERROR: Could not load: replay_srv.so ===
		+
		+	The replay library expects <tt>libcurl-gnutls.so.4</tt>.
		+
		+	If you are running 64-bit Debian or Ubuntu and attempting to run a 32-bit Team Fortress 2 instance, install the following package:
		+
		+	* <tt>libcurl4-gnutls:i386</tt> (on Debian 12 and older)
		+	* <tt>libcurl3t64-gnutls:i386</tt> (only on Debian 13)
		+	* <tt>libcurl4-gnutls:i386</tt> (on Debian 14 and newer, until further notice)

	=== Mann vs. Machine ===		=== Mann vs. Machine ===

@@ Line 62: / Line 62: @@
 iptables -A INPUT -p tcp --dport 27015 -j DROP
 </pre>
 = Platform-specific =

@@ Line 111: / Line 111: @@
 This allows both the game server and any connected clients to retrieve the latest version of the map through Steam.
-You can use that form in any place that accepts maps, such as the <tt>map</tt>, <tt>changelevel</tt>, and <tt>nextlevel</tt> commands, as well as the mapcycle file.  SourceMod itself has support to translate the names to their display forms and will do so in first-party plugins; third-party plugins and integrations (game server providers / panels and other software) may or may not support this functionality.
+You can use that form in any place that accepts maps, such as the <tt>map</tt>, <tt>changelevel</tt>, and <tt>nextlevel</tt> commands (including <tt>+map</tt> as a launch option), as well as the mapcycle file.  SourceMod itself has support to translate the names to their display forms and will do so in first-party plugins; third-party plugins and integrations (game server providers / panels and other software) may or may not support this functionality.
 '''Disregard any suggestions to subscribe to the map and copy the file to your game / fast download servers.'''  That is often repeated, yet bad advice, as:

@@ Line 109: / Line 109: @@
 [https://www.teamfortress.com/post.php?id=17214 As described in the patch notes shortly after the feature was added], Valve's intent is for server operators to use map names in the form <tt>workshop/${mapid}</tt>, where <tt>${mapid}</tt> is the ID of the map in the Workshop.   For example, [https://steamcommunity.com/sharedfiles/filedetails/?id=619869471 Sulfur] has an ID of 619869471, so you would specify it as <tt>workshop/619869471</tt>.
-This allows both the game server and any connected clients to retrieve the map through Steam.
+This allows both the game server and any connected clients to retrieve the latest version of the map through Steam.
-You can use that form in any place that accepts maps, such as the <tt>map</tt>, <tt>changelevel</tt>, and <tt>nextlevel</tt> commands as well as the mapcycle file.  SourceMod itself has support to translate the names to their display forms and will do so in first-party plugins; third-party plugins may or may not support this functionality.
+You can use that form in any place that accepts maps, such as the <tt>map</tt>, <tt>changelevel</tt>, and <tt>nextlevel</tt> commands, as well as the mapcycle file.  SourceMod itself has support to translate the names to their display forms and will do so in first-party plugins; third-party plugins and integrations (game server providers / panels and other software) may or may not support this functionality.
-'''Disregard any suggestions to subscribe to the map and copy the file to your game / fast download servers.'''  That is often repeated, yet bad advice.
+'''Disregard any suggestions to subscribe to the map and copy the file to your game / fast download servers.'''  That is often repeated, yet bad advice, as:
 === Games that aren't ===

@@ Line 105: / Line 105: @@
 === Using Workshop maps ===
-(This section has instructions specific to Team Fortress 2, and will likely not carry over to other games such as Counter-Strike: Global Offensive.)
+{{note|This section has instructions specific to Team Fortress 2, and will likely not carry over to other games such as Counter-Strike: Global Offensive.}}
 [https://www.teamfortress.com/post.php?id=17214 As described in the patch notes shortly after the feature was added], Valve's intent is for server operators to use map names in the form <tt>workshop/${mapid}</tt>, where <tt>${mapid}</tt> is the ID of the map in the Workshop.   For example, [https://steamcommunity.com/sharedfiles/filedetails/?id=619869471 Sulfur] has an ID of 619869471, so you would specify it as <tt>workshop/619869471</tt>.

← Older revision		Revision as of 05:27, 15 July 2023
Line 104:		Line 104:

	=== Using Workshop maps ===		=== Using Workshop maps ===
		+
		+	(This are instructions specific to Team Fortress 2; other games such as Counter-Strike: Global Offensive may have different instructions.)

	[https://www.teamfortress.com/post.php?id=17214 As described in the patch notes shortly after the feature was added], Valve's intent is for server operators to use map names in the form <tt>workshop/${mapid}</tt>, where <tt>${mapid}</tt> is the ID of the map in the Workshop. For example, [https://steamcommunity.com/sharedfiles/filedetails/?id=619869471 Sulfur] has an ID of 619869471, so you would specify it as <tt>workshop/619869471</tt>.		[https://www.teamfortress.com/post.php?id=17214 As described in the patch notes shortly after the feature was added], Valve's intent is for server operators to use map names in the form <tt>workshop/${mapid}</tt>, where <tt>${mapid}</tt> is the ID of the map in the Workshop. For example, [https://steamcommunity.com/sharedfiles/filedetails/?id=619869471 Sulfur] has an ID of 619869471, so you would specify it as <tt>workshop/619869471</tt>.

← Older revision		Revision as of 05:26, 15 July 2023
Line 102:		Line 102:

	Pass <tt>-enablefakeip</tt> in the server's launch options to enable. The server will then report "FakeIP allocation succeeded" at the end of startup; use that IP address / port combination in your game client to connect to the server. This allocation will change on every server startup.		Pass <tt>-enablefakeip</tt> in the server's launch options to enable. The server will then report "FakeIP allocation succeeded" at the end of startup; use that IP address / port combination in your game client to connect to the server. This allocation will change on every server startup.
		+
		+	=== Using Workshop maps ===
		+
		+	[https://www.teamfortress.com/post.php?id=17214 As described in the patch notes shortly after the feature was added], Valve's intent is for server operators to use map names in the form <tt>workshop/${mapid}</tt>, where <tt>${mapid}</tt> is the ID of the map in the Workshop. For example, [https://steamcommunity.com/sharedfiles/filedetails/?id=619869471 Sulfur] has an ID of 619869471, so you would specify it as <tt>workshop/619869471</tt>.
		+
		+	This allows both the game server and any connected clients to retrieve the map through Steam.
		+
		+	You can use that form in any place that accepts maps, such as the <tt>map</tt>, <tt>changelevel</tt>, and <tt>nextlevel</tt> commands as well as the mapcycle file. SourceMod itself has support to translate the names to their display forms and will do so in first-party plugins; third-party plugins may or may not support this functionality.
		+
		+	Disregard any suggestions to subscribe to the map and copy the file to your game / fast download servers. That is often repeated, yet bad advice.

	=== Games that aren't ===		=== Games that aren't ===