Add let-browser-players-join-cs16-server/en.md
Browse Source
1 changed file
with 56 additions and 0 deletions
let-browser-players-join-cs16-server/en.md
A
| @@ -0,0 +1,56 @@ | ||
| 1 | +--- | |
| 2 | +title: "Let Browser Players Join Your CS 1.6 Server (ReAuthCheck, ReUnion, HLDS)" | |
| 3 | +excerpt: "Members of counter-strike-boost.com can play CS 1.6 in their browser. If your server kicks them with \"Is Not Valid Auth (9)\" or \"STEAM validation rejected\", here is the exact setting to change for ReAuthCheck, ReUnion, plain HLDS and dproto." | |
| 4 | +category: "administration" | |
| 5 | +tags: "play in browser, reauthcheck, reunion, dproto, non-steam, server" | |
| 6 | +image: "" | |
| 7 | +read_time: "6 min read" | |
| 8 | +--- | |
| 9 | +<p>Members of counter-strike-boost.com can join CS 1.6 servers straight from their browser: they press the Play icon next to a server in our <a href="/servers">server list</a> and the game opens in a browser tab. To your server they are ordinary non-Steam players: protocol 48 with a RevEmu 2013 ticket. They reach your server through one of our relays, so your server sees the relay's address, not the player's.</p> | |
| 10 | +<p>Most servers that accept non-Steam players let them in with no changes. When a server kicks them, our server list shows a warning on its Play icon and your server's page tells you why. This guide fixes each case. Every fix below was tested on a real server with our browser client.</p> | |
| 11 | + | |
| 12 | +<h2>Which message do browser players get?</h2> | |
| 13 | +<ul> | |
| 14 | +<li><code>Error! Is Not Valid Auth (9).</code> right after the map loads: ReAuthCheck, detection method 9. See section 1.</li> | |
| 15 | +<li><code>Error! Is Not Valid Auth</code> with another number: another ReAuthCheck method. See section 1, same steps.</li> | |
| 16 | +<li>Browser players kicked or blocked once several of them are on the server: ReAuthCheck's limit per address. See section 2.</li> | |
| 17 | +<li><code>STEAM validation rejected</code>: the server only accepts Steam players. See section 4.</li> | |
| 18 | +</ul> | |
| 19 | + | |
| 20 | +<h2>1. ReAuthCheck: "Error! Is Not Valid Auth (9)."</h2> | |
| 21 | +<p>ReAuthCheck is a Metamod plugin for ReHLDS that checks every player's connection with ten detection methods. Method 9 flags our browser client and kicks it one or two seconds after the map loads. In ReAuthCheck's own log (<code>cstrike/addons/reauthcheck/logs/</code>) it looks like this:</p> | |
| 22 | +<pre><code>[Detect #9] -> Name [[CSB] Player] | Proto [48] | Auth [RevEmu2013] | ... | Build [10211]</code></pre> | |
| 23 | +<p>Open <code>cstrike/addons/reauthcheck/reauthcheck.cfg</code> and turn method 9 off:</p> | |
| 24 | +<pre><code>CheckMethod9 = 0</code></pre> | |
| 25 | +<p>Leave the other methods as they are and restart the server so the plugin reads the file again. On our test server (ReHLDS, ReUnion and ReAuthCheck 0.1.6 with its default settings) this was the only change needed: browser players joined and stayed.</p> | |
| 26 | +<p>The number in the message is the detection method. If your players see another number, for example <code>Is Not Valid Auth (3)</code>, set that method to 0 instead: <code>CheckMethod3 = 0</code>.</p> | |
| 27 | + | |
| 28 | +<h2>2. ReAuthCheck: let our relays through the limit per address</h2> | |
| 29 | +<p>Every browser player on the same relay reaches your server from that relay's address. By default ReAuthCheck lets only 3 players in per address (<code>MaxIpNum = 3</code>) and then bans the address for a few minutes (<code>PunishStringMaxIP = addip 180.0 [ip]</code>), which locks out every browser player on that relay. Add our relays to the white list at the end of <code>reauthcheck.cfg</code>:</p> | |
| 30 | +<pre><code>[List White IP] | |
| 31 | +87.106.40.132 | |
| 32 | +85.215.53.64</code></pre> | |
| 33 | +<p>The white list covers the limit per address (<code>CheckMaxIp</code>) and the reconnect limit (<code>CheckMaxDrop</code>). If you prefer, <code>CheckMaxIp = 0</code> turns the limit per address off for everyone, which also helps players who share one internet connection (internet cafes, NAT, VPN).</p> | |
| 34 | +<p>The detection ban commands (<code>PunishStringXFake</code> and the others) ban by <code>[ip]</code> too. With method 9 off they no longer catch browser players, but if a relay address still ends up banned, clear those lines: an empty value keeps the kick and drops the ban.</p> | |
| 35 | + | |
| 36 | +<h2>3. ReHLDS with ReUnion</h2> | |
| 37 | +<p>ReUnion is what lets non-Steam players in. Browser players use a RevEmu 2013 ticket, so check this line in <code>reunion.cfg</code>:</p> | |
| 38 | +<pre><code>cid_RevEmu2013 = 1</code></pre> | |
| 39 | +<p><code>1</code> is the default and gives each browser player their own SteamID. <code>5</code> rejects them. Also make sure <code>SteamIdHashSalt</code> is set to a random string of 16 or more characters: with <code>AuthVersion</code> 3 or higher ReUnion does not start without it, and then no non-Steam player can join.</p> | |
| 40 | +<p>Do not change <code>AuthVersion</code> on a server that already has players. It does not decide who can join, and changing it gives every non-Steam player a new SteamID, so admins, bans and stats tied to SteamIDs stop matching. A new server can use the value its ReUnion version recommends (3 in ReUnion 0.2.0.25, 4 in the newest builds).</p> | |
| 41 | +<p>New to ReUnion? See <a href="/tutorials/install-reunion">How to Install Reunion</a>.</p> | |
| 42 | + | |
| 43 | +<h2>4. Plain HLDS: "STEAM validation rejected"</h2> | |
| 44 | +<p>A stock HLDS server only accepts players with a Steam copy of the game, so it refuses every non-Steam player, browser players included, with <code>STEAM validation rejected</code>. No server.cfg setting changes that. You need a plugin that accepts non-Steam players:</p> | |
| 45 | +<ul> | |
| 46 | +<li><strong>ReHLDS with ReUnion (recommended).</strong> ReHLDS replaces the HLDS engine files and is still maintained. Install it, then ReUnion, as in <a href="/tutorials/install-reunion">How to Install Reunion</a>, and check section 3.</li> | |
| 47 | +<li><strong>dproto (old HLDS builds only).</strong> dproto 0.9.582 does not run on the current HLDS (build 8684): it stops at startup with <code>Sorry, this version of engine is not supported</code>. It only helps on a server that deliberately runs an older HLDS build. There, <code>cid_RevEmu2013 = 1</code> in <code>dproto.cfg</code> (the default) lets browser players in, and <code>5</code> rejects them.</li> | |
| 48 | +</ul> | |
| 49 | + | |
| 50 | +<h2>5. Check that it works</h2> | |
| 51 | +<ol> | |
| 52 | +<li>Restart the server after editing the files.</li> | |
| 53 | +<li>Sign in on counter-strike-boost.com, find your server in the <a href="/servers">server list</a> and press the Play icon next to its IP, or ask a member to. The game should load the map and stay in.</li> | |
| 54 | +<li>Once a browser player has played on your server for two minutes, the warning on its Play icon and on its page goes away by itself.</li> | |
| 55 | +</ol> | |
| 56 | +<p>Players: when a server kicks you with one of these messages, nothing on your side can fix it. Pick another server with the Play icon, or send this page to the server's owner. If the game cannot connect at all, see <a href="/tutorials/fix-browser-game-cant-connect">Fix: Play in Browser Can't Connect</a>.</p> | |
| 0 | 57 |
