There's an interesting article on Kotaku on cheating in multiplayer games, focusing on malfeasance in Battlefield 3, DICE's military shooter sequel. Well, malfeasance is our term, the article takes an almost sympathetic tone, characterizing the cheaters it specifically portrays as regular players, and relating their complex rationalizations of how they are somehow more justified than garden-variety cheaters. The article also takes a surprisingly informative approach to details on this, choosing to provide links to cheat providers, prices of various exploits, and even de facto reviews of their effectiveness.

DG wrote on Jun 18, 2012, 14:40:The response by the dev is a total joke as well. The best way to combat cheating is to look at stats? Wipe first then ban for second offence? They're only even trying to get the most flagrant to buy a second copy.

Whats even more hilarious is that the new BF3 premium package lets cheaters wipe their stats. Its like they are trying to give cheaters a reason to buy it.

ItBurn wrote on Jun 18, 2012, 14:46:To me it definitely looks like hit detection is client side. If you go into cover while being shot at, you still get hit long after you're hidden. Because of the lag, your enemy still sees you even tho you just hid in your game. That or, it's really strange handling of hit detection or broken position interpolation.

That in and of itself is not evidence of client side hit detection. That happens in CS and TF2 which are server based hit detection, because of the whole lag prediction model they use.

Now, it may well be that BF3 hit detection is all client side, I don't know. I'm just saying that bit of evidence doesn't mean much.