BF2S Forums how did this get past PB?

I've seen one guy witch had that kind of hack too... it sucks

iamtheoneneo wrote:

ok so i was on karkand last night in an apc, enemy guy was at the flag so naturally i shot him - he didnt die, so me being me just thought my accuracy sucked and carried on , so then he decides to standup - face me and just stand there, so naturally i shoot the crap out of him , rockets etc nope he doesnt die and then he just walks away.
i call him a f***ing hackor (which i get kicked and have to join again for swearing - doh)
so question is this is obviously a hack and a big one at that so how come PB didnt recognise it and plus it cant be from ***security site as they dont do invincibility hacks do they?

ok 1 was you on ranked Server?

as I can gurantee you there is No Life hack for BF2 ( u can modify files that makes your helth go down really really slow i.e instead of givin u 0.10 damage it will give you 0.0001 damage which will make your helth go down Slow )

Few things for anyone to even atempt to do that on ranked Server Will get Boosted As files have been changed

1 of the reasons why PB dosent Bust Certen hacks is cas the hack Modifys it self when PB scans it, let me asure you that PB have Most of the Hack websites for BF2 and They will test all the hacks ( even if they will buy it )

Thats when U see this private hackers getin Busted and moaning about it on hack forums


Hacker dosent cear how long it will take for his hack to be ditected all he wants to do is get sumcash out of it, why do u think every new hack that comes out has titel PB Proof what happend to otherhacks that were PB proof ?


I stated in loads of other threds about hacks why people shouldent download them Not only u installing other hiden softwere on your PC but most of the time you dont even have a clue what u install ( dont be thinking cas its payd nothing extra will be installed )

I use2 make them I know how they work if you have any more questions post Up below peace Boris

sinir wrote:

Here is a scenario, Blue/Red tag bug with FF turned off...  Unkillable "enemies"...

Ok that could be 2end Version

Hello all,

First post here. I have been reading this forum on and off for a while, but registered to add my 2c to this.

I don't think it's a hack (but read on...), rather some net code breakdown. Logged on a server running Ghost Town yesterday, spawed as AT on the north helo base as SAS. Just as I did, an enemy comes up the the stairs, so I fill him up with DAO lead... nothing, smoke and all, but the guy is still standing. Thinking it's because I just spawed and I "lag" because of it, I just go on, and empty the whole magazine, point-blank... nothing still, exept the guy happilly kills me with a couple shots (after I emptied my gun on him).

I respawn at the same place, only this time on the roof, as he is taking off in the helo, so I get the AT out and shoot one... no effect still, except I find I don't have to wait for reload to shoot another one, and another, and another. As I do this, the guy simply takes off slowly, turns around. Last thing I see before dying is his squadmate spawning as gunner and said guns firing me into oblivion... Although I did hit his helicopted 3-4 times with AT rockets, it doesn't show any sign of damage.

So I quit the server, thinking, wow, this is really really odd. This is the very first time anything like this has ever happened to me. Granted I don't have enormous amount of hours in BF2, but still, in 220+ hours ingame, you get to see many things. It seemed like something was "out of synch". Checked my ping before leaving, and it was normal (ie below 75).

Oh, and just to state the obvious, I play honorably.

Maybe this is a not so common bug that's starting to appear? The problem I've experienced sounds at lot like what "neo" experienced.

Happened to my buddy for a round.  His bullets didn't effect anybody, all his kills came from claymores or nades.  It fixed itsself when the round was over.  Is this some packet loss or client/server miscommunication?  It could very well be a hack but anecdotally it sounds like a bug that happens every-so-often.