Closed GoogleCodeExporter closed 8 years ago
Suggestions:
cam_collision (Default: 1)
Minimum: 1
Prevent players from looking through walls
c_thirdpersonshoulderheight (Default: 5.0)
Minimum: 0.0
Maximum: 25.0
Prevent players from using very high/low values which can let you look on
roofs, floors below, and pretty much everywhere even through walls without
disabling cam_collision. Survivors could search the map for items already
during ready-up for example.
c_thirdpersonshoulderoffset (Default: 20.0)
Minimum: -20.0
Maximum: 20.0
Similar to c_thirdpersonshoulderheight
c_mindistance (Default: 30)
Minimum: 30
Maximum: 30
c_maxdistance (Default: 200)
Minimum: 200
Maximum: 200
cam_idealdist (Default: 150)
Minimum: 30
Maximum: 150
Prevent players from zooming in/out too far, can be abused to zoom out far to
get an overview over the current part of the map (including rooftops), or to
zoom in far, whether you have a sniper rifle or not. Especially lame with a
sniper, since it lets you zoom in unlimited distances while bypassing fog - you
could easily snipe a tank on hard rain for example that you normally couldn't
see - while the poor tank wonders how you still hit him and loses control...
Original comment by Dynastic...@googlemail.com
on 14 Apr 2011 at 9:33
Attachments:
[deleted comment]
I've heard anecdotal reports of HR runners hitting tanks hidden deep in fog on
c3m1. This may indeed be a serious exploit that needs patching.
Original comment by ryan.del...@gmail.com
on 15 Apr 2011 at 7:13
http://code.google.com/p/confogl/source/detail?r=85736bb8b9e52b7c22ced222a1398c5
e7f0d3790
Feel free to test and make sure it all works.
Original comment by Canada.R...@gmail.com
on 27 Apr 2011 at 6:05
Using it on my server, it works.
I have chosen the limits so users with the defaults don't get touched, and (as
we don't block thirdperson completely atm) someone who might be using
thirdpersonshoulder to play will not get kicked as long as he doesn't zoom out
too far or manipulate his camera in others ways that would let him see too much.
Original comment by Dynastic...@googlemail.com
on 1 May 2011 at 2:57
Original issue reported on code.google.com by
Dynastic...@googlemail.com
on 14 Apr 2011 at 5:08