Slashdot Mirror
Game Developers Cracking Down on Cheating
Hector73 writes "ZDNet has an article discussing a growing concern for the makers of on-line video games. Cheaters and trolls are making it harder for casual users and newbies to get hooked on the on-line versions of games. Considering that on-line gaming may become the major revenue source for game makers over the few years, maybe they will actually do something about it."
They need to introduce some sort of peer rating system, where each individual rating doesn't mean much. Something like -1 Troll, +1 Good Sportsmanship, etc.
You can be sure that I won't be buying any games from the people mentioned in that article, and I suggest everyone else who values their freedom do the same.
"I don't know that atheists should be considered citizens, nor should they be considered patriots." - George Bush
Damn the Emperor!
Then the people with the cheats would be ranked "Best" and would only get to play with others that cheat or superhuman players.
I'll assume you suck, so this solves the problem for you, but I'm "superhuman" at some games I play. The best players get "rewarded" by being forced to play against all the cheaters? Oh joy. Thanks but no thanks, I'll pass.
(I occationally enjoy kicking the crap out of a cheater without cheating myself, but not all the time. And some cheats are unbeatable.)
-
- - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
Disney World also sacrifices some of its paying customers to ensure the rest of them have a quality experience. And so does SixFlags.
>Code needs to be written to self protect. Once an intrusion or a hack is detected, it determines the nature of the hack, and forbids the next attempt.
// function which checks its current program for modification
// perform checks ...
// we passed the check (TRUE) //We failed
It is 100% impossible for a given program determine if it has been hacked if the person who is trying to hack it is the administrator/root user of the machine. Is this clear enough? You have control over everything the program sees because you can modify every portion of it. Watch:
int check_self() {
if (we_passed) {
return TRUE;
}
else return FALSE;
}
int run() {
if (check_self()) {
continue();
}
else
In this situation the "run()" function calls the "check_self()" function to see if the current program is still OK. However all the hax0r would have to do would be to change a single byte, FALSE (0) to TRUE (1), in the program with a special editor and the program would appear to pass the self test, even though it didn't.
If we aren't the superuser on the system we can protect ourselves by not allowing the programs to be modified and preventing ordinary users from accessing their address space, like SUID/SGID binaries in UN*X or programs started by other users.