Just stumbled across this article addressing the MAV exploit, its not a super reliable source but it is something to be hopeful for.
Battlefield 3′s Gameplay Designers, Gustav Halling and Alan Kertz talk MAV exploits and the differences between BF2 versions of the Back to Karkand Maps and their BF3 counter-parts.
Gustav Halling was recently asked if the rather goofy MAV exploit has been patched yet. For those who don’t know, the MAV exploit, which has given rise to hilarious videos like this, allows players to ride on top of it to lift themselves to generally unreachable areas of any given map. Halling responded, “not yet, will be fixed in next [patch],” confirming that it will, indeed, be patched. Hopefully, this fix will be included in the long awaited February patch. No more free rides for you recon players, it seems.
Recently, Alan Kertz spoke of some of the differences of the Battlefield 2 versions of the Back to Karkand maps and their Battlefield 3 remakes. He was asked why some vehicles did not appear on these new maps as they did in Battlefield 2. For example, Gulf of Oman is missing Transport Helicopters on the Russian side, while there is also a missing Humvee on Strike at Karkand and Sharqi Peninsula. Kertz explained, “we made some tweaks to update the maps for BF3, some of the original designs don’t directly translate,” meaning certain decisions had to be made in regards to the similarity of vehicle layouts.
Also a little on the punkbuster issues:
Errors of PC players being kicked from playing Battlefield 3 by Punkbuster are currently being looked into, but it turns out that there could me more to the situation than meets the eye.
“Game disconnected: you were kicked by Punkbuster errors are being looked into right now.” Stated Community Manager, Daniel Matros recently. He added that it “looks like it has something to do with Kaspersky, Avira and Norton AV.” For those who don’t know, Punkbuster is an anti-cheat system used for the PC platform to help keep hackers and cheaters from doing what they do. Speaking of which, Matros also mentioned that a “new PB version [is] out today. If you haven’t updated, it’s worth doing so as well.” At least it might help.
Interestingly, and most unfortunately, the problem seems to go much deeper than these surface issues, however. Looking at the Battlelog profiles of those claiming to have been unrightfully banned by PB, you’ll notice that they are, indeed, clean and do not use hacks or are not cheating. The real problem is that it looks like the ban itself could be a hacking attempt. According to these forums, a group of hackers have found a “security hole” in the PB system and are now trying to bring it to the attention of those in charge of security by banning players on the Battlelog. So far, they claim to have already banned over 150 Battlefield 3 players.
Upon discovering his account has been unrightfully banned, one user explains his situation on the Battlelog forums and warns others: “My account name has TWO GUID’s, which is impossible. I also run two servers that stream to GGC, and the MD5 tool hack that is linked to my account was caught from the UK and Austria with IP’s that do not match mine. Someone out there is using some sort of GUID scanner and using it for cheats/hacks.”
This is obviously a lose-lose situation and it is truly unfortunate that it had to come to this. While flaws in the system should be brought to the attention of those in charge, doing so at the expense of innocent gamers is certainly not the right way to do it. Let’s hope that the situation can be resolved quickly and those who have been banned unjustly will receive their accounts back