Mon May 12, 2003 3:20 pm
Cheating on Elite
It seems the new server code handled it, but not immediately.
The player in question is muh_2k. He logged on as level one, then was kicked in about 2 mins for "possible cheating". As this COULD be a bug, I caught him when he next logged in and informed him that the server thought he was cheating. When I sent the messages, he was rank 1. When I looked again about 20 seconds later, he was rank 79.
He managed to stay playing for a good 3-5 mins @ rank 79, then was once again kicked for "possible cheating". I'm glad the safeguards are catching such cheaters, but ... in 5 mins he could (if given more than one 5 min period) buy almost anything in the game, provided he could get to the proper base. Perhaps I just don't know when the cheat checks happen, and they really DO prevent against the small nightmare possibility I stated, but in case not, I'm blathering about publicly about it. : ))
Edit: As I was typing this, he tried again, this time just giving himself enough cash for rank 12. Same results : ) Kicked in 3-5 mins.
Edit again, cuz I'm amused: Seems he went to search for easier fish. : ) Hope the patch goes public soon. ; )
Edit: Ok, I swear I won't edit this again. But, a suggestion. Currently, "possibly cheating" characters only see the "disconnected from server" message. They have NO clue that the server code interpreted their actions as cheating. In order to keep this a server-side fix (as booting chars requires a client-side fix to inform them of the "possible cheating"
, I would suggest a 10-15 second window between the console "Possible cheating detected: <name>", and their actual kick. That would at least give them time to read the message, rather than being booted before they can read it. A possible addition would be to ALSO message the player (before kick), of the "possible cheating", say once per 3-5 seconds, until the kick? That way we'd be SURE they got the message....
Sure, it'll take a little longer before they're kicked, but at least they'll know that they were kicked, rather than assuming they just lost their connection. Just a thought : ) The information that he was being kicked auto via server code seemed to deter muh_2k in short order, so I'm feeling that in this case, information of the offense is a good thing in terms of deterrents : )))
Edited by - Hellif on 12-05-2003 16:22:45
Edited by - Hellif on 12-05-2003 16:27:10
Edited by - Hellif on 12-05-2003 16:50:36
The player in question is muh_2k. He logged on as level one, then was kicked in about 2 mins for "possible cheating". As this COULD be a bug, I caught him when he next logged in and informed him that the server thought he was cheating. When I sent the messages, he was rank 1. When I looked again about 20 seconds later, he was rank 79.
He managed to stay playing for a good 3-5 mins @ rank 79, then was once again kicked for "possible cheating". I'm glad the safeguards are catching such cheaters, but ... in 5 mins he could (if given more than one 5 min period) buy almost anything in the game, provided he could get to the proper base. Perhaps I just don't know when the cheat checks happen, and they really DO prevent against the small nightmare possibility I stated, but in case not, I'm blathering about publicly about it. : ))
Edit: As I was typing this, he tried again, this time just giving himself enough cash for rank 12. Same results : ) Kicked in 3-5 mins.
Edit again, cuz I'm amused: Seems he went to search for easier fish. : ) Hope the patch goes public soon. ; )
Edit: Ok, I swear I won't edit this again. But, a suggestion. Currently, "possibly cheating" characters only see the "disconnected from server" message. They have NO clue that the server code interpreted their actions as cheating. In order to keep this a server-side fix (as booting chars requires a client-side fix to inform them of the "possible cheating"
, I would suggest a 10-15 second window between the console "Possible cheating detected: <name>", and their actual kick. That would at least give them time to read the message, rather than being booted before they can read it. A possible addition would be to ALSO message the player (before kick), of the "possible cheating", say once per 3-5 seconds, until the kick? That way we'd be SURE they got the message....
Sure, it'll take a little longer before they're kicked, but at least they'll know that they were kicked, rather than assuming they just lost their connection. Just a thought : ) The information that he was being kicked auto via server code seemed to deter muh_2k in short order, so I'm feeling that in this case, information of the offense is a good thing in terms of deterrents : )))
Edited by - Hellif on 12-05-2003 16:22:45
Edited by - Hellif on 12-05-2003 16:27:10
Edited by - Hellif on 12-05-2003 16:50:36