Randomized quad spawn

[divVerent]

As for wallhack: as if we would tell you publicly.

[alpha]

As for wallhack: as if we would tell you publicly.

So says dear Fuhrer! He and his clan can use secret nexuiz hacks (colorprint, now wallhack, what else?). You can't! Obey or else!

[parasti]

1) Add feature X.
2) Spread the word.
3) Let people get used to it.
4) Declare it's a cheat.
5) ???
6) Profit!!!

My question is, what makes it so difficult to stop at step 1 and add some preventive measures that allow feature X to be used only when some cvar is set (sv_cheats, developer, if_i_set_this_i_am_a_cheater)? Is it because step 5 is just too much fun or what.

[Waterlaz]

Oh and btw... there is one more thing this topic showed:
http://www.alientrap.org/forum/viewtopic.php?t=4651
People don't want randomized times. And that's pretty much it.
We can look at the pole here for cleaner resaults but you can get the idea from that topic.

[Mr. Bougo]

As for wallhack: as if we would tell you publicly.

So says dear Fuhrer! He and his clan can use secret nexuiz hacks (colorprint, now wallhack, what else?). You can't! Obey or else!

Oh hi thar <3

Thanks for the hilarity.

He and his clan just set up this false topic to put some doubt into your suspicion: http://www.forums.alientrap.local/viewtopic.php?t=3939

My question is, what makes it so difficult to stop at step 1 and add some preventive measures that allow feature X to be used only when some cvar is set (sv_cheats, developer, if_i_set_this_i_am_a_cheater)? Is it because step 5 is just too much fun or what.

Actually, it's so ridiculously easy, that reverting the prevention in the source would be even easier. So it's out of question.

[PinkRobot]

So says dear Fuhrer! He and his clan can use secret nexuiz hacks (colorprint, now wallhack, what else?). You can't! Obey or else!

It's true! Ooooooowwwwwowowowowwwww it's so true...

/me breaks down in tears

[Mr. Bougo]

Also, the color thingy was successfully attacked from multiple sides. It's leaked.

But I think people just don't want to share it with you.

[parasti]

Actually, it's so ridiculously easy, that reverting the prevention in the source would be even easier. So it's out of question.

And why would I revert it? I think you misunderstood. Somebody just said using r_showsurfaces is cheating; I often use r_showsurfaces because I'm on a GF4MX and most maps are ridiculously demanding, so basically that makes me a cheater without me even being aware of it. If I had to set "developer" or some other cvar to use r_showsurfaces, or even if the cvar description just said, "using this is cheating", I would not bother using it (actually in the case of r_showsurfaces, I would, but I would know I'm walking a thin line). Accusing legitimate players of cheating is simply not a good way to treat your community.

[Mr. Bougo]

I didn't say you would cheat
But I didn't undersand what you meant. Yes, I agree that there should be more emphasis put on the fact that r_showsurfaces and friends are meant for debugging purposes.
I thought you wanted to have some kind of "anti-cheat" that would disable these cvars in some conditions (e.g. online games), but this would not stop a cheater I think.

[tundramagi]

As for wallhack: as if we would tell you publicly.

So says dear Fuhrer! He and his clan can use secret nexuiz hacks (colorprint, now wallhack, what else?). You can't! Obey or else!

Lol, last week you were the God of Nexuiz. You decided if something was "wanted" or "not wanted". Now you peddle yourself as an opressed serf. Look how quickly your "demenor" has changed, lol.