While reviewing configs for some leagues, the ETPro team noticed that most of the configs were ported pretty much straight from RTCW.
The problem is that many of the cvars no longer work in ET, or they work differently.
remove: r_uifullscreen
afaik this no longer works in ET, so checking it is pointless.
remove: r_ext_NV_fog_dist
this doesnt work the same in ET anymore. see r_nv_fogdist_mode
add: pb_sv_cvar r_nv_fogdist_mode INCLUDE NV’
this is the correct fog check for ET. note, pb generates bogus (but harmless) violation warnings on this.
add:pb_sv_cvar r_primitives IN 0 2
3 could be used as a cheat…
remove: pb_sv_task 300 600 pb_sv_cvarsrch com_maxfps
remove: pb_sv_task 600 600 pb_sv_bindsrch com_maxfps
the com_maxfps sniper cheat no longer exists in ET (recoil is fps independent in ET)
Maybe you can make a full list with all ET punkbuster cvar`s and some comment lines which explains why to use the setting, i know there are already some list but most are incomplete or not 100% related to ET.
Also officialy locked cvar`s would be handy to know because they can be unlocked and abused and PB wont notice it fast enough, pb detection does happen between 30 minutes and 4 hours of playtime.
I also like to know why PB needs to check the client cvar`s every 10-30 secs (pb_sv_cvarfreq = 2-6 times a minute, 6=every 10 secs, 2=every 30 secs.), i did mail evenbalance about this issue but didnt get any responce yet, this cvar check freq. lags our servers every 30 secs)
sorry for going offtopic just a bit here. First of all thank you for your servers, I play on them very often since the ping is always good. (I’m dutch too, will keep my post in english though so others know what I’m talking about too). Also your servers are 10vs10 which is my favorite.
Secondly, are your servers v1.02? If so did you remove complaint filing for engineer/field op? I hate it when I artillery the bridge constructor in Fueldump and my teammates file complaints (really, ffs, artying the tank/constructor is the best thing to do in that map, why are my teammates there anyway) and I could think of some other reasons to remove complaint filing.
Your indeed going offtopic, but 2 answer the question, both servers run Shrub MOD (sorry Bani, didnt have time yet to try out your probably outstanding MOD) and i have 2 wait for an update from their side.
Server is running at Uni Utrecht (fastest university link in NL, thanks sis )
I’ve an article on ET cvar restrictions here, I’d welcome your input bani - particularily some detail on r_primitives IN 0 2 (PM?) or anything else you think missing/inaccurate/whatever (edit: esp. timenudge, since about everything I find on that seems hopelessly opinionated and rarely even loosely based on something like facts).
baneh keeps poking me to chime in, so I’ll un-lazy now…
This check is actually better than checking r_ext_NV_fog_dist for both RtCW and ET, just to comment. It lets people use the GL_NV_fog_distance extension, but still keeps them from setting r_nv_fogdist_mode to GL_EYE_PLANE (which prevented fog from rendering in RtCW.) The problem seems to be fixed in ET, but it still accepts the incorrect value for r_nv_fogdist_mode, so I’ve been using the check just to be on the safe side.
r_primitives 3 causes bizarre texture rendering problems in RtCW and ET, which could potentially be used to make players higher contrast in the distance.
Let’s see, what else?
For both RtCW and ET, I recommend the following check:
pb_sv_cvar cg_errordecay IN 0 500
cg_errordecay controls how fast a prediction error is decayed off to smooth out any jerkiness. A prediction error is, very basically, what occurs when the client and server disagree on the location you’re in. Unfortunately, there are many problems with RtCW’s prediction code (several of which carried over into ET) that make it easy to cause prediction errors, so by setting cg_errordecay really high and exploiting any of the prediction errors, you can effectively move your camera away from yourself far enough to see through walls. It doesn’t really seem to be possible to generate enough error within 500ms to give yourself any advantage.
If you’re using etpro, you don’t need this check unless you’re being extremely paranoid–not only does etpro cap the value of this cvar to 0-500, but we’ve fixed several cases where prediction errors could occur (all of the easy ones to exploit that we know about), and plan to fix more in the future.
Since I’ve mentioned a few RtCW checks here, I might as well add this one, which affects RtCW only:
pb_sv_cvar cg_reticleType IN 1
A bug in RtCW will will cause the binocular reticle to stop being drawn if cg_reticleType is 0, enabling players to see the full zoomed screen.
That’s all I can think of off the top of my head, though…
On some of the more controversial cvars, e.g. timenudge, I haven’t really looked at the code enough to give a good opinion here, to be honest. We have come to the conclusion that using timenudge doesn’t make much sense with antilag enabled, though.
Like i already did post in another topic about PB lagging our server i will also display our PB settings atm.
Already did find some which can be removed according to Bani and Rain so i will remove those or // them out.
Our settings:
“rate” IN 2500 25000
“snaps” IN 20 40
“cl_maxpackets” IN 15 100
“cl_timenudge” IN -50 0
“cl_freelook” IN 1 1
“m_pitch” OUT -0.015 0.015
“m_yaw” IN -0.022 0.022
“cg_bobup” IN 0 0.005
“cg_errordecay” IN 100 100
“com_maxfps” OUT 0.00001 40
“r_flares” IN 0 1
“r_picmip” IN 0 3
“r_picmip2” IN 0 3
“r_gamma” IN 0 3
“r_intensity” IN 0 1.5
“r_overbrightbits” IN 0 3
“r_mapoverbrightbits” IN 0 3
“r_uifullscreen” IN 0 0 <---- can be removed ?
“r_ext_nv_fog_dist” IN 0 0 <---- should be changed to?
“r_overbrightbits” IN 0 4
“r_mapoverbrightbits” IN 0 4
“cg_shadows” IN 0 1
“r_rmse” IN 0 75 <---- not in ET ?
“cg_fov” IN 80 125
“r_allowextensions” IN 1 1
“r_softwareGL” IN 0 0
“r_wolffog” IN 1 1
“r_shownormals” IN 0 0
“r_showtris” IN 0 0
“r_lightmap” IN 0 0
added them in, tho left errordecay at IN 100 and just added a note. Left in rmse as nothing happened when checking in 1.02 but it did in 1.00 - so just left a note that it can be removed in 1.02 servers.
at a glance i think you dont need:
“r_picmip” IN 0 3
“r_picmip2” IN 0 3
“r_gamma” IN 0 3
“r_intensity” IN 0 1.5
“r_overbrightbits” IN 0 3
“r_mapoverbrightbits” IN 0 3
“r_uifullscreen” IN 0 0 <---- can be removed ?
“r_ext_nv_fog_dist” IN 0 0 <---- should be changed to?
“r_overbrightbits” IN 0 4
“r_mapoverbrightbits” IN 0 4
“r_rmse” IN 0 75 <---- not in ET ?
“r_allowextensions” IN 1 1
“r_softwareGL” IN 0 0
“r_wolffog” IN 1 1
“r_shownormals” IN 0 0
“r_showtris” IN 0 0
“r_lightmap” IN 0 0
Users can change back values changed with forcecvar unless the variables are cheat protected or read only, so that wouldn’t be ery effective.
We’re thinking about adding something along these lines a bit down the road, though, 'cause we think it’s much more preferable to snap a cvar into range than it is to kick for it.
prob with that (imho) is you take the decisions out of the hands of tourneys etc and into yours, unless they can be set server side. having said that, i’m guessing youse are talking about definite “cheat” cvars (e.g. high errordecay) rather than the debateables (e.g. timenudge), so um k im talking rubbish :p.
also, since sniper recoil no longer dependent on fps, is this restriction about pointless?
pb_sv_cvar com_maxfps OUT 0.00001 40
DG i want to know which of this cheat protected cvar`s are still used in ET, because cheat protected doesnt exist/work 100% anymore, there are already cheat protected cvar unlockers which are sometimes detected by PB but mostly after a period of several palying hours.
Thats also the reason why i did put them into our list.
you can remove like half of those:
