Page 4 of 4

Re: Server.cfg

Posted: Sat 4. Apr 2026, 16:18
by Bino45
Hello,
Just a heads-up, an inconsistency has been detected: on the "gun game only" server.

It's running at tick66, but the min/max values ​​are set to tick100. ;)

Please double-check your server.cfg file. ;)

Cheers!

Re: Server.cfg

Posted: Tue 14. Apr 2026, 01:38
by Bino45
Hello,

So, how did the test go? (even though it was done on a less frequented server).

Thanks

Re: Server.cfg

Posted: Wed 6. May 2026, 01:49
by Bino45
Forget about scripts or plugins for the problem I've been raising about on your servers for years... There's a server command for this specific issue.

`sv_competitive_minspec`, value 0 or 1.

Here's Valve's own definition for this command: Enable to force certain client variables to minimum/maximum values ​​to help prevent competitive advantages.

This clearly means that not forcing certain values ​​on the client side gives them a competitive advantage if they're misconfigured.

Of course, this assumes that the `server.cfg` file contains the correct values.

Here's what this command does:

"sv_competitive_minspec" enforces the following restrictions on clients when set to 1:

r_drawdetailprops 1
r_staticprop_lod (-1 to 3)
fps_max minimum 60 (or 0)
cl_detailfade minimum 400
cl_detaildist minimum 1200
cl_interp (0 to 0.031)
cl_interp_ratio (1 to 2)


These are the cl_interp and cl_interp_ratio values, directly from Valve, within which players MUST operate in order NOT to gain an unfair advantage over other players...

There are far too many players whose hitboxes are so misaligned...

I can't convince you any better to review the netcode of your configurations, which are incorrect across all your tick66s ;)