Re: Verifying Client Data....
In not so technical terms, it is making sure that you didn't edit the games files manually. If you were to edit them, it would change the files MD5 hash (digital signature that could be compared to your fingerprint). When the scan is taking place, it is basically going to retrieve the md5 hash of certain files for the BF2 game and compare them against known legit ones for the game.
Again, that was all in not so technical english as to not confuse you with more than you needed to know just to get what amounts to the same answer. As in, I tried to break it down as simple as possible. Here is more technical information on it if you would like to look into it more, or were just looking for a more technical answer: http://www.akadia.com/services/md5.html
You would be better off playing on servers with Pure Mode (aka Content Check) running, than not. It is very easy for people to cheat in servers like that, I am not going to get into detail either, but there are a ton of things you can do to this game to get an illegitimate advantage over others that Pure Mode stops.
As for the reason it doesn't appear to be working on Linux, it would be a guess, but it is either broke or never was made in the first place. I am sure someone that is running a nix box could answer, just have to find someone that is.
Personally, EA-Dice could have taken a different approach on the client verification system. They should have done a portion of the MD5 checks during 'Account Login' to check the common files of the game that would always be in use. The rest of the checks should take place during mapload and only check the items that are needed for that map. Not to mention, they could have slimmed down what was all being checked by trimming down some of the unnecessary searches. In short, the major part of the checking would be done before you actually started playing maps (one time) and the rest would be very quick small checks between maploads. But that is just wishful thinking.
In not so technical terms, it is making sure that you didn't edit the games files manually. If you were to edit them, it would change the files MD5 hash (digital signature that could be compared to your fingerprint). When the scan is taking place, it is basically going to retrieve the md5 hash of certain files for the BF2 game and compare them against known legit ones for the game.
Again, that was all in not so technical english as to not confuse you with more than you needed to know just to get what amounts to the same answer. As in, I tried to break it down as simple as possible. Here is more technical information on it if you would like to look into it more, or were just looking for a more technical answer: http://www.akadia.com/services/md5.html
You would be better off playing on servers with Pure Mode (aka Content Check) running, than not. It is very easy for people to cheat in servers like that, I am not going to get into detail either, but there are a ton of things you can do to this game to get an illegitimate advantage over others that Pure Mode stops.
As for the reason it doesn't appear to be working on Linux, it would be a guess, but it is either broke or never was made in the first place. I am sure someone that is running a nix box could answer, just have to find someone that is.
Personally, EA-Dice could have taken a different approach on the client verification system. They should have done a portion of the MD5 checks during 'Account Login' to check the common files of the game that would always be in use. The rest of the checks should take place during mapload and only check the items that are needed for that map. Not to mention, they could have slimmed down what was all being checked by trimming down some of the unnecessary searches. In short, the major part of the checking would be done before you actually started playing maps (one time) and the rest would be very quick small checks between maploads. But that is just wishful thinking.
Comment