Regarding the PQR ban

[moor2]

sorry for silly question, but does that apply for the old, discontinued PropablyEngine, or that "new" Possibly Engine? (or both)

[Teh Canadian]

sorry for silly question, but does that apply for the old, discontinued PropablyEngine, or that "new" Possibly Engine? (or both)

I am not a dev.. and I suck at anything technical... but... I would go to guess that they both used the same 'patching' method.

~Spazzer

[Jadd]

They added a new scan in the morning for CGGameUI__CanPerformAction.

Seem like a direct attempt to catch probably engine, inst that the address that they patched?

Why they never used WardenMon in the first place is beyond me. This wouldn't be as much of an issue if they had.

[xoreaxeax]

No offense, but ... really? Is Warden (better: Blizzard) that dumb?

Regarding to Wardenmon, Warden already scans at 0x008C764A (3 bytes) and now there's a second scan couple of bytes later. Am I not getting something? What stops me from e.g. injecting my epilogue just one byte after or several bytes before that scanned range? If I'm correct, in this specific case it all comes down to pushing 1 (or was it 0? Too tired, can't remember) into eax, clean up if necessary, and just return. At least if you want to keep it very simple.

Can someone please tell me that I'm totally wrong and warden is way, way more sophisticated than this new and stupid just-for-one-known-hack-that-happens-to-use-those-5-bytes-scan they've implemented?

[Ninjaderp]

Aw shit I used PE earlier tonight, but I went and got Firehack and used it couple of hours ago. Im gonna be so bummed if I get banned >_<

[Jadd]

No offense, but ... really? Is Warden (better: Blizzard) that dumb?

Regarding to Wardenmon, Warden already scans at 0x008C764A (3 bytes) and now there's a second scan couple of bytes later. Am I not getting something? What stops me from e.g. injecting my epilogue just one byte after or several bytes before that scanned range? If I'm correct, in this specific case it all comes down to pushing 1 (or was it 0? Too tired, can't remember) into eax, clean up if necessary, and just return. At least if you want to keep it very simple.

Can someone please tell me that I'm totally wrong and warden is way, way more sophisticated than this new and stupid just-for-one-known-hack-that-happens-to-use-those-5-bytes-scan they've implemented?

Put it this way: If you don't edit the memory in the scanned range, you'll avoid being banned. I'd like to tell you you're wrong, but you've hit the nail on the head.

[JUANNY]

Knowing that blizz is aware of PE and PQR why would anybody even consider going back to them-sry to say that it is silly unless you really dont care bout your wow account-there are no safe solutions yet HB remains safer then most tho ive found that it is slower then both PE and PQR but slow wow play is better then a perm ban

[svs]

Aw shit I used PE earlier tonight, but I went and got Firehack and used it couple of hours ago. Im gonna be so bummed if I get banned >_<

Isnt FH patches the same adresses?

[l0l1dk]

Isnt FH patches the same adresses?

No, FH doesn't patch where the scan is. Even if it did, it has Warden protection so the scan wouldn't detect it.

[Justinepally]

soooo basically anyone that has injected PE today is ****ed and it's only a matter of time till the hammer falls?

[MaiN]

No offense, but ... really? Is Warden (better: Blizzard) that dumb?

Regarding to Wardenmon, Warden already scans at 0x008C764A (3 bytes) and now there's a second scan couple of bytes later. Am I not getting something? What stops me from e.g. injecting my epilogue just one byte after or several bytes before that scanned range? If I'm correct, in this specific case it all comes down to pushing 1 (or was it 0? Too tired, can't remember) into eax, clean up if necessary, and just return. At least if you want to keep it very simple.

Can someone please tell me that I'm totally wrong and warden is way, way more sophisticated than this new and stupid just-for-one-known-hack-that-happens-to-use-those-5-bytes-scan they've implemented?

Put it this way: If you don't edit the memory in the scanned range, you'll avoid being banned. I'd like to tell you you're wrong, but you've hit the nail on the head.

They don't care about your private hack. The point of Warden is that, as soon as you release a public hack and it becomes popular, they can completely dynamically add a new scan that will catch your hack. It doesn't matter if you avoid current scans as they in 2 days can add the scan that catches you.

[wowmerq]

Edited. /10

[rocambole]

How this new warden affects Mac users? I only used PE in my hackintosh.

Edit: Also, Is it possible to use PE addon with a different unlocker as Firehack?

[Opacho]

Edit: Also, Is it possible to use PE addon with a different unlocker as Firehack?

Yes. 10char