Sugar, a key is sent to the server in this format:įor an original StarCraft key, the first DWORD is 0x0000000C. It could also explain why you are unable to detect it, and why, despite things being unchanged in both versions of the game, that it still happens.Īnother idea: What if they planned this for quite some time and some sort of system had existed in the game for awhile, but didn't become active until recently? If that is possible, it could explain things in relation to converted keys working versus purchased "new-style" keys not. All keys from 1111111111111 and lower are translated normally on the server-side, but when keys 1111111111112 and above are sent to the server, it initiates some kind of system that detects the game's validity, such as a Warden-style element. Hdx, could it be something server-side? Maybe since the servers know which keys are valid and which are not, isn't it possible for them to just set the new ones to translate a certain way on their end that is different than the previous ones? For example: SC Key 1111111111111 is converted to ABCDEFGHIJKLMN. But use at own risk CDKeys that are unique, and purchased as 2 chr cdkeys are the ones causing the problems. What it most likely is, is our implementations probably assume something, which in generall was true, but isn't for these new keys.Īnyways, IN GENERAL, cdkeys that are converted from 13 to 26 chrs, are fine. Joe, I know, the game also uses length of key to determine which to decode with.īut why it is decoding improperly, I do not know, until I get the time/resources to compare the real implementation of the decode method with our implementation of it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |