---
title: "The 25 CS 1.6 Server Cvars You Actually Need"
excerpt: "A no-filler reference to the server cvars that matter on a public CS 1.6 server: identity, networking, rates, downloads, logging and security, with sane values."
category: "administration"
tags: "cvars, config"
image: ""
read_time: "8 min read"
---
<p>A CS 1.6 server exposes hundreds of cvars, and most are noise you will never touch. This is the short list that actually determines whether your server is findable, plays smoothly, and is safe to run in public. Put these in <a href="/tutorials/setup-server-cfg-cs16">server.cfg</a>; the round-specific <code>mp_</code> cvars have their own <a href="/tutorials/mp-cvars-reference">reference</a>.</p>

<h2>1. Identity and access</h2>
<table>
<thead><tr><th>Cvar</th><th>Example</th><th>What it does</th></tr></thead>
<tbody>
<tr><td><code>hostname</code></td><td>"My CS 1.6 Server"</td><td>Name shown in the browser and master list.</td></tr>
<tr><td><code>rcon_password</code></td><td>"long-random"</td><td>Remote admin password. Make it long; RCON is brute-forceable.</td></tr>
<tr><td><code>sv_password</code></td><td>""</td><td>Join password. Empty = public.</td></tr>
<tr><td><code>sv_contact</code></td><td>"admin@example.com"</td><td>Contact address in server info.</td></tr>
<tr><td><code>sv_region</code></td><td>3</td><td>Master-list region (0 US-East ... 3 Europe ... 255 world).</td></tr>
</tbody>
</table>

<h2>2. Visibility and networking</h2>
<table>
<thead><tr><th>Cvar</th><th>Example</th><th>What it does</th></tr></thead>
<tbody>
<tr><td><code>sv_lan</code></td><td>0</td><td><strong>Must be 0</strong> to heartbeat the master list. 1 = LAN only.</td></tr>
<tr><td><code>sv_timeout</code></td><td>60</td><td>Seconds before a silent client is dropped.</td></tr>
<tr><td><code>sys_ticrate</code></td><td>1000</td><td>Target server FPS ceiling — see <a href="/tutorials/sys-ticrate-truth">the truth about it</a>.</td></tr>
<tr><td><code>pausable</code></td><td>0</td><td>Prevent clients pausing the server.</td></tr>
</tbody>
</table>
<p><code>sv_lan 0</code> is the one people forget; with it at 1 the server never appears online and clients hit a LAN error. See <a href="/tutorials/fix-server-not-in-master-list">server not in the master list</a>.</p>

<h2>3. Rates — the settings that decide how it feels</h2>
<table>
<thead><tr><th>Cvar</th><th>Example</th><th>What it does</th></tr></thead>
<tbody>
<tr><td><code>sv_maxrate</code></td><td>25000</td><td>Max bytes/sec per client. 0 = uncapped; cap it.</td></tr>
<tr><td><code>sv_minrate</code></td><td>15000</td><td>Floor so low-rate clients do not choke everyone.</td></tr>
<tr><td><code>sv_maxupdaterate</code></td><td>101</td><td>Max snapshots/sec to a client. Cannot exceed server FPS.</td></tr>
<tr><td><code>sv_minupdaterate</code></td><td>30</td><td>Floor for update rate.</td></tr>
<tr><td><code>sv_maxspeed</code></td><td>320</td><td>Movement speed ceiling. Standard is 320.</td></tr>
</tbody>
</table>
<p><code>sv_maxupdaterate</code> is bounded by your actual server FPS: promising 101 updates on a 60 FPS server is a lie the engine cannot keep, and you get choke on the scoreboard (see <a href="/tutorials/fix-choke-loss-scoreboard">choke and loss</a>).</p>

<h2>4. Downloads</h2>
<table>
<thead><tr><th>Cvar</th><th>Example</th><th>What it does</th></tr></thead>
<tbody>
<tr><td><code>sv_allowdownload</code></td><td>1</td><td>Let clients download missing content.</td></tr>
<tr><td><code>sv_allowupload</code></td><td>1</td><td>Let clients upload their sprays/logos.</td></tr>
<tr><td><code>sv_downloadurl</code></td><td>"http://dl.example.com/cs"</td><td>FastDL mirror. See <a href="/tutorials/fastdl-setup-guide">FastDL setup</a>.</td></tr>
</tbody>
</table>

<h2>5. Logging and security</h2>
<table>
<thead><tr><th>Cvar</th><th>Example</th><th>What it does</th></tr></thead>
<tbody>
<tr><td><code>log</code></td><td>on</td><td>Enable logging to <code>cstrike/logs/</code>.</td></tr>
<tr><td><code>mp_logmessages</code></td><td>1</td><td>Log chat, useful for moderation.</td></tr>
<tr><td><code>mp_logdetail</code></td><td>3</td><td>Log attacks and kills (bit 1 + bit 2).</td></tr>
<tr><td><code>sv_cheats</code></td><td>0</td><td>Must be 0 in public; 1 enables cheat cvars.</td></tr>
<tr><td><code>sv_filterban</code></td><td>1</td><td>1 = banned IDs are blocked (ReHLDS/HLDS ban filter).</td></tr>
<tr><td><code>sv_voiceenable</code></td><td>1</td><td>In-game voice on/off.</td></tr>
<tr><td><code>decalfrequency</code></td><td>30</td><td>Seconds between spray decals; raise to curb spray spam.</td></tr>
</tbody>
</table>
<p>That is 25 cvars that do real work. On <a href="/tutorials/install-rehlds-on-linux">ReHLDS</a> you also get hardening cvars worth adding on top, but the list above is the universal floor.</p>

<h2>6. How to think about the groups</h2>
<p>Treat these five groups as a checklist for any new server. <strong>Identity</strong> is what players and the master list see, and a weak <code>rcon_password</code> here is the single most dangerous omission — a guessed RCON password hands an attacker the whole server, so make it long and random and never reuse it across servers. <strong>Visibility and networking</strong> decides whether the server is reachable at all; <code>sv_lan 0</code> plus an open UDP 27015 (see <a href="/tutorials/cs16-server-firewall-ports">which ports to open</a>) are non-negotiable for a public box.</p>
<p>The <strong>rate</strong> group is where most "my server feels laggy" complaints actually live. The rates are a contract between server and client: the server offers a ceiling, the client requests up to it, and the real delivered rate is the minimum of what both allow and what the server FPS can sustain. Set <code>sv_maxrate</code> and <code>sv_maxupdaterate</code> deliberately rather than leaving them at defaults, and keep the update rate within reach of your true server FPS — the details are in <a href="/tutorials/sys-ticrate-truth">the sys_ticrate guide</a>. The <strong>downloads</strong> and <strong>logging/security</strong> groups are the ones people bolt on later and regret not setting from day one: FastDL keeps map changes fast, and logging is the only reason you will be able to answer "who did that?" a week after the fact.</p>
<p>A final habit worth forming: comment each block in <code>server.cfg</code> so six months from now you know why a value is what it is. A cvar with no comment is a cvar nobody dares change.</p>

<h2>Common errors</h2>
<ul>
<li><strong>Server invisible online</strong> — <code>sv_lan 1</code>. This is the number-one cause.</li>
<li><strong>Choke/loss for everyone</strong> — <code>sv_maxupdaterate</code> promises more than server FPS delivers. Match it to real FPS.</li>
<li><strong>Wrong region in the browser</strong> — <code>sv_region</code> set to the wrong number, so region filters hide you.</li>
<li><strong>RCON compromised</strong> — a short <code>rcon_password</code>. Use a long random string and consider <code>sv_rcon_*</code> failure limits on ReHLDS.</li>
<li><strong>Cvar "does nothing"</strong> — it is being re-set later by <code>amxx.cfg</code> or a per-map config. Trace the execution order.</li>
</ul>

<h2>Verification</h2>
<p>After editing <code>server.cfg</code>, change the map and read values back in the console — typing a cvar name with no argument echoes its current value:</p>
<pre>sv_lan
sv_maxupdaterate
sv_downloadurl</pre>
<p>Confirm each shows what you set. Then check the server appears in the internet browser under the right region, and that a client joins without choke. If a value refuses to stick, see <a href="/tutorials/fix-server-cfg-not-executing">why server.cfg is not executing</a>.</p>