Tutoriale

Tell a cvar-caused kick, ban or crash apart from an ordinary crash, bisect the batch you just enabled, and keep a ReHLDS hardening baseline that does not punish real players.

How fps_max really works in CS 1.6, why it is capped at 100 until you set fps_override, how FPS affects bunnyhopping physics, and how to lock a stable frame rate.

Use sv_consistency and mp_consistency to force consistent models, and query_client_cvar in an AMX Mod X plugin to catch clients running cvars used to cheat.

A reference to the mp_ gameplay cvars that shape a CS 1.6 round, with correct units, sane defaults, and which ones only exist under ReGameDLL.

Why your sv_maxrate and sv_maxupdaterate seem to have no effect, which of these cvars need ReHLDS/ReGameDLL, the min/max interplay, and how to confirm clients actually get the rate.

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.

How the four end-of-map limits interact, which need ReGameDLL, why whichever fires first wins, and how to design a map flow that ends cleanly and advances the rotation.

ReHLDS adds cvars stock HLDS never had — for timing, anti-flood and network behaviour. Here are the ones that affect performance and stability, and how to set them without breaking old plugins.

Exactly what each download cvar does, how the server and client flags interact, why sv_downloadurl needs the cstrike path, and how to stop clients joining with missing textures.

The server-side rate cvars are a ceiling on what every client is allowed to use. Set them wrong and you either choke good connections or invite abuse. Here are the values that make sense.