A tour of the underused server.cfg lines that improve performance, security, and operational sanity.
Most server.cfg files are 80% boilerplate copied from a tutorial. There is gold buried in the other 20%.
set onesync on for under 32 players, set onesync_population true so NPCs sync correctly, and on Infinity-tier servers set onesync_distanceCullVehicles true to stop streaming vehicles nobody can see.
sv_endpointprivacy true hides player IPs from public server queries — turn it on. sv_authMaxVariance 1 and sv_authMinTrust 5 tighten the trust score requirements; useful if you are seeing a lot of trolls with brand-new Cfx accounts.
sv_maxClients should match your real capacity, not your aspirations. sv_pureLevel 0 keeps client mods unrestricted; setting it to 1 or 2 blocks asset replacements depending on level. Use this carefully — many graphics packs players use will fail at higher pure levels.
set sv_enforceGameBuild 2944 (or your target build) locks players to a specific GTA version, preventing build mismatches with newer DLC vehicles. set sv_listingHostOverride lets you control the IP shown on the public server browser if your VPS is behind a load balancer.
sv_lan true on a public server (you will skip every Cfx anti-cheat check). sv_scriptHookAllowed true (you will get cheaters in the door instantly). And don't paste add_principal lines for accounts you don't recognize — that is the easiest way to give yourself a backdoor.
Spend an hour reading the entire server.cfg reference on the Cfx docs. You will find at least three lines you should add and two you should remove. That alone is worth more than most tweak-my-config-for-me services.
Written by
Alex Johnson
Questions? Browse our products or contact us
