Open GoogleCodeExporter opened 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
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
"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
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
Original issue reported on code.google.com by
igorpana...@gmail.com
on 23 Aug 2009 at 7:00