Re: Tournament bans
It'd be easier to have it all embedded within the game. For example, it would say 9/1/2007 6:22:14PM on the lower left-hand side, and on the lower-right hand side, it'd show something like ef2a70deb3543f913eb70d7f56364cb2
Only the admins of the site would know exactly how the information from the score would be arranged for encryption. You'd simply go to the scorechecker, input 9/1/2007 6:22:14PM for a given user, and see the score they got if it was indeed recorded. Easy!
For the more complicated cases where the score was not recorded (or, if someone was cheating):
Say someone posted a score of a Neomax AAA at 9/1/2007 6:22:14PM, and it gives the string 6bdbcf4fbceffbdac75b13564a63bb08 in the lower right-hand corner. You'd go to the checker function, type in the user's name, their score breakdown, the time from the screenshot, as well as 6bdbcf4fbceffbdac75b13564a63bb08. It would spit back "Score is OK" if the encryptor from the input matched, and "Score is fake" if not. This means the score was legitimate even if it wasn't recorded anywhere in the database, and otherwise means the score never happened.
There is no way to get around it because you wouldn't know how the string is arranged where the encryption is taking place -- it's something only the admins would know. It renders Photoshopping of screenshots 100% useless.
It'd be easier to have it all embedded within the game. For example, it would say 9/1/2007 6:22:14PM on the lower left-hand side, and on the lower-right hand side, it'd show something like ef2a70deb3543f913eb70d7f56364cb2
Only the admins of the site would know exactly how the information from the score would be arranged for encryption. You'd simply go to the scorechecker, input 9/1/2007 6:22:14PM for a given user, and see the score they got if it was indeed recorded. Easy!
For the more complicated cases where the score was not recorded (or, if someone was cheating):
Say someone posted a score of a Neomax AAA at 9/1/2007 6:22:14PM, and it gives the string 6bdbcf4fbceffbdac75b13564a63bb08 in the lower right-hand corner. You'd go to the checker function, type in the user's name, their score breakdown, the time from the screenshot, as well as 6bdbcf4fbceffbdac75b13564a63bb08. It would spit back "Score is OK" if the encryptor from the input matched, and "Score is fake" if not. This means the score was legitimate even if it wasn't recorded anywhere in the database, and otherwise means the score never happened.
There is no way to get around it because you wouldn't know how the string is arranged where the encryption is taking place -- it's something only the admins would know. It renders Photoshopping of screenshots 100% useless.
Comment