nikotine40 / confogl

Automatically exported from code.google.com/p/confogl
0 stars 0 forks source link

Values that confogl should check #85

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
There are many ways to cheat in l4d2 and the last update was a nice start to 
fix this but there are many other values that have to be controlled.
Here is a list of values that can be misused for cheating:

cl_drawhud = 1
cl_entityreport = 0
cl_glow_blur_scale = 3
cl_leveloverview = 0
cl_phys_timescale = 1.0
cl_showevents = 0

fog_override = 0
hidehud = 0

mat_dxlevel >= 80
mat_fillrate = 0
mat_fullbright = 0
mat_measurefillrate = 0
mat_wireframe = 0

r_aspectratio = 0
r_colorstaticprops = 0
r_drawothermodels = 1
r_flashlightfov = 53.0
r_shadowwireframe = 0
r_drawentities = 1
r_drawrenderboxes = 0
r_drawparticles = 1
r_drawbrushmodels = 1
r_drawclipbrushes = 0
r_drawdecals = 1
r_skybox = 1
r_visocclusion = 0

snd_show = 0
snd_visualize = 0

sv_cheats = 0
sv_consistency = 1

vcollide_wireframe = 0

_____________

Particularly mat_fullbright is often used and has to be blocked.

Best regards,
Saphirchen

(P.S. <3 confogl =) )

Original issue reported on code.google.com by beranek....@gmail.com on 30 Aug 2010 at 8:59

GoogleCodeExporter commented 8 years ago
Most of those are cheat cvars, which can't be changed by clients anyway when 
sv_cheats is off. Are you sure checking for all of these is necessary?

Original comment by prodigysim@gmail.com on 31 Aug 2010 at 2:48

GoogleCodeExporter commented 8 years ago
As long as u cant check for clientplugins all these variables have to be fix. 
For example the POV Plugin 
(http://www.l4dmods.com/index.php?option=com_joomloads2&view=package&pid=212&Ite
mid=32) was such a thing untill valve added values for it. Like in this plugin 
it is possible to change cheatvalues without sv_cheats=1

Original comment by beranek....@gmail.com on 31 Aug 2010 at 5:12

GoogleCodeExporter commented 8 years ago
There's a number of other ways we could deal with client plugins besides 
blocking any cvars they could use. I'm pretty sure with the same plugins it 
would be easy for them to block the cvar from being queried by the server.

1. Valve has talked about removing DLL addons from clients (not sure if this 
has happened)
2. addons_eclipse_content 0 support for non-official servers is coming
3. We could check for sourcemod/metamod cvars, and kick those clients
4. Rather than building in a massive anti-cheat, people can add KAC or some 
other Anti-Cheat to their configurations.

We aren't going to add these cvar checks to default confogl, but feel free to 
add them to your own config.

Original comment by prodigysim@gmail.com on 31 Aug 2010 at 5:19