[Release] UltimateWoW - The Best Free WoW Hack Available

[kupoo]

Experiencing the same problem with binding keys.

[Jadd]

I'll look into it but in the meantime go to the forums to post support - it's where I check before here.

[ciano1]

got banned within the minute - shame though as it worked like a charm
ill try with another account, i could of been just unluky

[Jadd]

got banned

You're the first.

[Nesox]

Or maybe Jetlag did the velocity hack poor, now did u do it the right way?

[Robske]

Or maybe Jetlag did the velocity hack poor, now did u do it the right way?

How i dereference pointr?

[Nesox]

How i dereference pointr?

int* Foo = 0xDEADBEEF;
*Foo = 0;

[Jadd]

int* Foo = 0xDEADBEEF;
*Foo = 0;

Why do you keep posting here?

[Cypher]

How i dereference pointr?

You need to take the green pill. The red and blue ***** are lies.

int* Foo = 0xDEADBEEF;
*Foo = 0;

int Lol;

__asm
{
mov eax, 0xDEADBEEF
mov eax, [eax]
mov Lol, eax
}

Amidoinitrite?

[Hellson]

Hi, you must be an idiot, I'm Cypher. Nice to meet you.

Please refrain from posting in the future (or preferably, living). Kthx.

It's like i'm playing diablo 2 all over again.

[kynox]

got banned within the minute - shame though as it worked like a charm
ill try with another account, i could of been just unluky

I lol'd IRL.

[HuЯЯ1cΛиΞ™]

Your hack is really cool, even though too much WI like same key bindings and so on, wich shows you might got the leaked source code of an older version of WI.
A closer look proves it, some parts of your code have EXACT same variable names and values like WI 1.3.1 so don't say you didn't C+P anything..
Don't worry I never leak anything but to stay on the safe side, I would recommend to improve your protection.



Oh and if you read this, UnknOwned, nice to see that the real WI is more protected now aka "C:\Newsecurity\encryptthis.txt" and stuff, haha ya I just couldn't resist trying it again.

PS:
Even though I had your source, I did NOT leak it anywhere so don't shout at me please.

[Jadd]

Your hack is really cool, even though too much WI like same key bindings and so on, wich shows you might got the leaked source code of an older version of WI.
A closer look proves it, some parts of your code have EXACT same variable names and values like WI 1.3.1 so don't say you didn't C+P anything..
Don't worry I never leak anything but to stay on the safe side, I would recommend to improve your protection.



Oh and if you read this, UnknOwned, nice to see that the real WI is more protected now aka "C:\Newsecurity\encryptthis.txt" and stuff, haha ya I just couldn't resist trying it again.

PS:
Even though I had your source, I did NOT leak it anywhere so don't shout at me please.

I never copy/pasted anything apart from the names of functions.

Shove that where it fits.

[Nesox]

Why do you keep posting here?

Because we all love you soo much

int Lol;

__asm
{
mov eax, 0xDEADBEEF
mov eax, [eax]
mov Lol, eax
}

Amidoinitrite?

!! I think so ! ; i can haz anti anti api huuk detection plx`?

[Robske]

[COLOR=DarkOrange]

!! I think so ! ; i can haz anti anti api huuk detection plx`?

Why so hard nesox? Just delete scan.dll

You should add a scan.dll-deleter to this pack jetlagjad!