Blizzard blocking Interact()... sometimes.

[RiseAndShine]

It's from the BlackMagic library, a class with some utility functions for Getting/Suspending threads.

[jbrauman]

It's from the BlackMagic library, a class with some utility functions for Getting/Suspending threads.

Thanks :wave:

[Sillyboy72]

while I can't directly help... I can say that going down a similar path (pause/inject&execute/resume) only lead to tears and destruction.

Just get your DLL into wowz process and hook EndScene. way better.

[jbrauman]

while I can't directly help... I can say that going down a similar path (pause/inject&execute/resume) only lead to tears and destruction.

Just get your DLL into wowz process and hook EndScene. way better.

HAX!

But in all seriousness I'm not that good. I cant even read assembly, let alone try to debug Wowz. But I know what you mean, I'm getting random DC's now (although I think it has something to do with writing my facing like, 100 times per second in some bits of my code =/ )

[Sillyboy72]

But in all seriousness I'm not that good. I cant even read assembly, let alone try to debug Wowz.

You should at least think about it. So many things are so much easier this way. It's easy enough to get your DLL injected (I just inject the same way you are... but inject a call to LoadLibrary my dll). And once you do that... pretty much everything is easier.

I'm getting random DC's now (although I think it has something to do with writing my facing like, 100 times per second in some bits of my code =/ )

There is definately something to your theory here. I have a bot flying around looking for Everfrost Chips... and get DC'd every once in awhile when I try to "fight the bot" my manually adjusting directions. Dunno if its too many big jumps in facing or what.

[RiseAndShine]

You should at least think about it. So many things are so much easier this way. It's easy enough to get your DLL injected (I just inject the same way you are... but inject a call to LoadLibrary my dll). And once you do that... pretty much everything is easier.

But isn't that detected by warden? Or is that just an issue with public bots?

[kynox]

But isn't that detected by warden? Or is that just an issue with public bots?

Public. Warden relies on module names and module signatures to detect injected DLLs.

[Xarg0]

Public. Warden relies on module names and module signatures to detect injected DLLs.

Warden also monitors some offsets to detect patches 'n stuff, so you can get banned with a private bot/hack if you're patching offsets watched by warden, if you don't implement counter measures.
WoWX Hooks the Warden Doscann method and removes all patches befor it calls the original Doscann function and reapplies them afterwards, so all patches made by WoWX are invisible to the Warden, but if Blizzard implements a stack trace inside the Warden they would be able to check if doscann was hooked, by checking the adress that the call came from and I can't think of an easy way to hide the calling adress.

[kynox]

Warden also monitors some offsets to detect patches 'n stuff, so you can get banned with a private bot/hack if you're patching offsets watched by warden, if you don't implement counter measures.
WoWX Hooks the Warden Doscann method and removes all patches befor it calls the original Doscann function and reapplies them afterwards, so all patches made by WoWX are invisible to the Warden, but if Blizzard implements a stack trace inside the Warden they would be able to check if doscann was hooked, by checking the adress that the call came from and I can't think of an easy way to hide the calling adress.

a) Theres a dormant stack trace in Warden
b) Warden could still detect WoWX if it wanted to.