vloup / sgfork

Automatically exported from code.google.com/p/sgfork
GNU General Public License v2.0
0 stars 1 forks source link

LIst of new cheat-protected variables #29

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Overall description of the new feature:
There are more q3-commands in, which allow to add fancy visual
effects

what i like about SmokinGuns, is that everyone has to play with 90 fov - 
this adds some realism and especially fairness - but this has to be done 
consequently also with other settings (e.g. r_fastsky allows to make sky 
black)

in case you consider to remove ancient q3-variables which allow players to 
get advantage over others by dragging down realistic look, i will post a 
list of variables which could be considered to be either removed, capped 
into certain limits or locked

Variables to control the new feature:
r_fastsky
+any others?

Which game parts are involved:
binary?
N/A
game?
N/A
cgame?
N/A
ui?
N/A
media?
N/A

Original issue reported on code.google.com by igorpana...@gmail.com on 23 Aug 2009 at 7:00

GoogleCodeExporter commented 9 years ago
Write the list of variables, please.
Set status as accepted after.

Original comment by igorpana...@gmail.com on 23 Aug 2009 at 7:02

GoogleCodeExporter commented 9 years ago
Well, the problem is that anybody can modify is client and "uncheat" any 
variable.
r_fastsky can be seen as a way to do less things for you computer.

Anyway, some variable could be usefull for mappers or testers to see what's 
wrong
here or here.

Original comment by kikc...@gmail.com on 24 Aug 2009 at 9:51

GoogleCodeExporter commented 9 years ago
"modify" the client is something that most players won't do.

I took r_fastsky as an example, since it got a big visual effect by taking away 
some
realism. Variables that should be locked need to be discussed first of course. 
But
you need to keep in mind that there are plenty of variables that will cause
wallhack-alike effects when set to extreme values. These are mainly the 
settings that
need to be capped.

About variables useful for mappers and testers: you are totally right about 
that, and
this is why they should be set to 'CHEAT', so they can be used still by loading 
the
map via /devmap

I will get up a list after my exams which will be in some weeks. And then we'll
discuss which settings should be capped/locked/removed.

I don't think this Issue is a big problem at the very moment, but as soon as 
the game
gets more competetive you will see loads of people try gaining advantage by 
using
exploits.

Original comment by mortijs-...@yahoo.de on 24 Aug 2009 at 12:06

GoogleCodeExporter commented 9 years ago
The client changing is other issue.
Here will be done only list of cheat protected variables.

I'm bot sure that r_fastsky is cheat.. Some players have slow PCs.
But I'll wait for list to discuss.
You could do the document to describe whem all and provide detailed explanation 
why 
they have to be cheat-protected.

Original comment by igorpana...@gmail.com on 6 Sep 2009 at 10:25