sv_tags
links to other VDC articles. Please help improve this article by adding links that are relevant to the context within the existing text. January 2024
sv_tags is a console variable available in all 
Source games.
This was introduced as of the 1.0.2.0 update on Feb 28, 2008.
Added "Custom" tab to the server browser * Servers can now specify metatags describing the custom rules they've adopted * Players can use tag filtering to find servers running the custom rules they want to play * Added options for servers who want to become custom games: Disable critical hits * tf_weapon_criticals), eliminate respawn times (mp_disable_respawn_times), and raise maxplayers above 24
Note: Since the introduction of the sv_tags cvar, the custom tab has been removed from the server browser, thus adding custom tags using the sv_tags cvar will no longer cause a server to be added to the custom tab or removed from the internet tab.
Usage
Custom server tags can be added by supplying the sv_tags cvar with a comma-delimited list of tags:
sv_tags "tag1,tag2,tag3"
Providing a value for the sv_tags cvar will result in the value being appended to the automatically set tags. For example if you set sv_tags to "foo" and you have alltalk on, the server tags will be displayed as "alltalk,foo".
List of tags
This is a list of the official tags, but servers are allowed to use additional tags.
| tag | cvar | quickplay eligible | Explanation |
|---|---|---|---|
| alltalk | sv_alltalk 1 | Yes | Voice chats are not team specific |
| bots | N/A | Yes | Serverside bots are used (both tf_Bot and bot) |
| birthday | tf_birthday 1 | Birthday mode, birthday themed gibs as well as the birthday ball | |
| fadetoblack | mp_fadetoblack 1 | Dead players will have their screen faded to black instead of spectating | |
| friendlyfire | mp_friendlyfire 1 | No | Teammates can hurt each other |
| gravity | sv_gravity not equal to 800 | No | Lower or higher gravity than normal |
| highlander | mp_highlander 1 | No | Teams are limited to only one player per class |
| increased_maxplayers | maxplayers > 24 | Gradual penality | More players than the valve recommended maximum |
| nocrits | tf_weapon_criticals 0 | No | Weapons do not crit |
| nodmgspread | tf_damage_disablespread 1 | No | Weapon damage is not randomized |
| noquickplay | tf_server_identity_disable_quickplay 1 | No | No quickplay users allowed |
| norespawntime | mp_disable_respawn_times 1 | No | Respawn waves are disabled |
| replays | replay_enable 1 | Yes | The server supports replays |
| _registered | Multiple | Mandatory | The server is registered with Valve |
| respawntimes | mp_respawnwavetime not equal to 10.0 | No | |
| suddendeath | mp_stalemate_enable 1 | Yes | Heavy boxing occurs instead of stalemates |
| mvm | N/A | Separate pool | Mann vs Machine mode |
Bugs
- If you set mp_respawnwavetime to 10, you will still get the tag. It must be 10.0.
- tv_enable 1 will also cause increased_maxplayers to activate, even if maxplayers is set to 4. As soon as the bot joins, you get the tag.