[Ak01]

bump. Anyone got new address ?

[mrbrdo]

It should be 008D86F0 in 2.4.2.

[kynox]

Just so you guys are aware, warden is scanning this memory offset, and the wallclimbing offset. Any editing of these on live will result in a ban.

[Queue]

Does this speed up the whole server? Just a stupid question, but on the private server Im playing, when I used the speedhack, the people started talking something about a change in speed... Or then Im just paranoid :P

[torn68]

Originally Posted by Chazwazza

> AAARRGGGHHH, ITS A FLOAT. NOT AN INT!!!!

I know, it makes me want to cry.
I've given up, it seems stupidity will always trump intelligence and logic.

I wish you'd quit with the rant.

Note that, on a 32-bit Intel cpu, sizeof(int) == sizeof(float) == 4 bytes.

So whether you choose to view those 4 bytes as a float or a 4 character array ("string") or simply 4 bytes, the content of those bytes is the same. The only difference is the way CheatEngine is displaying it to you (using certain bits as a mantissa, etc. for float.)

It is perfectly valid to interpret those 4 bytes for "max jump height" as float or 4 bytes. If you use float, then you'll be using modified values like -10 (just a bit higher), -30 (jump even higher), -100 (jump much higher), -300 (visit the moon) instead of the huge values the original poster gave.

If you set it as a "4 bytes" value, you'll be using much larger decimal values, which is what the original poster chose to do.

For what it's worth, I used this hack yesterday to jump from Ashenvale into Hyjal , and I used both "4 bytes" and "float" representation to test it.

So get off the soapbox about float vs 4 bytes.

Oh, and I was instantly teleported out of Hyjal both times. I guess Blizzard replaced the 2-minute(?) "No Man's Land" debuff with this instant GTFO teleport. Phuckers.

-torn68

[kynox]

Originally Posted by torn68

I wish you'd quit with the rant.

Note that, on a 32-bit Intel cpu, sizeof(int) == sizeof(float) == 4 bytes.

So whether you choose to view those 4 bytes as a float or a 4 character array ("string") or simply 4 bytes, the content of those bytes is the same. The only difference is the way CheatEngine is displaying it to you (using certain bits as a mantissa, etc. for float.)

It is perfectly valid to interpret those 4 bytes for "max jump height" as float or 4 bytes. If you use float, then you'll be using modified values like -10 (just a bit higher), -30 (jump even higher), -100 (jump much higher), -300 (visit the moon) instead of the huge values the original poster gave.

If you set it as a "4 bytes" value, you'll be using much larger decimal values, which is what the original poster chose to do.

For what it's worth, I used this hack yesterday to jump from Ashenvale into Hyjal , and I used both "4 bytes" and "float" representation to test it.

So get off the soapbox about float vs 4 bytes.

Oh, and I was instantly teleported out of Hyjal both times. I guess Blizzard replaced the 2-minute(?) "No Man's Land" debuff with this instant GTFO teleport. Phuckers.

-torn68

As true as that is, its stupid and retarded to use an int.

[torn68]

Originally Posted by kynox

As true as that is, its stupid and retarded to use an int.

lol well that's surely a matter of opinion. The point is, the original poster's HOWTO is valid.

You mentioned "the wallclimbing offset" -- what is this?

EDIT: Found it in a post by

Originally Posted by SCSI73rm1n8r;

008A00C8: BB,8D,24,3F -> A4,86,F3,BE
This seems to give a better result by changing the constant associated with the maximum climb angle

-torn68

[Cypher]

Originally Posted by torn68

I wish you'd quit with the rant.

Note that, on a 32-bit Intel cpu, sizeof(int) == sizeof(float) == 4 bytes.

So whether you choose to view those 4 bytes as a float or a 4 character array ("string") or simply 4 bytes, the content of those bytes is the same. The only difference is the way CheatEngine is displaying it to you (using certain bits as a mantissa, etc. for float.)

It is perfectly valid to interpret those 4 bytes for "max jump height" as float or 4 bytes. If you use float, then you'll be using modified values like -10 (just a bit higher), -30 (jump even higher), -100 (jump much higher), -300 (visit the moon) instead of the huge values the original poster gave.

If you set it as a "4 bytes" value, you'll be using much larger decimal values, which is what the original poster chose to do.

For what it's worth, I used this hack yesterday to jump from Ashenvale into Hyjal , and I used both "4 bytes" and "float" representation to test it.

So get off the soapbox about float vs 4 bytes.

Oh, and I was instantly teleported out of Hyjal both times. I guess Blizzard replaced the 2-minute(?) "No Man's Land" debuff with this instant GTFO teleport. Phuckers.

-torn68

Are you retarded? That just proves you don't actually know how or why this hack works, and you're simply copy-pasting offsets and thinking you're an 'uber hacker'. I realize that they're both the same size in memory, but that doesn't change the fact that they're DIFFERENT DATA TYPES. The fact that you think just because it 'works no matter how you read it' proves that you should stay away from reverse engineering and programming and just stick to downloading click and point hacks written by those of us who aren't idiots.

EDIT: Because you probably won't work it out, I'll explain it. The value is the decimal (as opposed to radian) representation of the cosine of the maximum angle the player is able to climb up. ie cos(50) = 0.642..etc. That is how it's supposed to be used, as a float, if you check how it's used you'll see that's how its referenced in the code and even someone who managed to pass high school math would know enough about trig to realize what is going on. So while you may be able to change it to random values when reading as an integer and have it work that's just retarded, the reason it works is because you're changing the number so that it turns out that the offset reads in memory as cos(90) or larger (ie, <= 0). Please, either do your research or just stfu. Thank you.

EDIT2: Was referring in this post to the wallclimb offset (because thats what was mentioned in the post above), but the same applies to the jump height. They're both floats, and if you're reading/writing to them as otherwise then you obviously have no idea what you're doing and are too stupid to do anything but copy the work of those of us with half a brain then molest it.

EDIT3: I just realised another retarded thing you were saying, you're saying that '4 bytes' is a data type, what you actually mean is an INTEGER. which neither of the values are, they're floats, and they're not the same.

[loulou2]

i got banned >:X

[Eternalblood]

i got banned >:X

My friend accidently logged with this and got a temp ban

This will get you banned

[Shynd]

Kynox already stated that Warden specifically looks at this offset. You'd have to be retarded to use this on a retail server.

[kynox]

Originally Posted by Shynd

Kynox already stated that Warden specifically looks at this offset. You'd have to be retarded to use this on a retail server.

Quoted for great justice!

[Etherea]

Originally Posted by Chazwazza

Are you retarded? That just proves you don't actually know how or why this hack works, and you're simply copy-pasting offsets and thinking you're an 'uber hacker'. I realize that they're both the same size in memory, but that doesn't change the fact that they're DIFFERENT DATA TYPES. The fact that you think just because it 'works no matter how you read it' proves that you should stay away from reverse engineering and programming and just stick to downloading click and point hacks written by those of us who aren't idiots.

Chazwazza, torn68 brings up a perfectly valid point and there is no reason to flame him. Whether you write a float, int or a char[4] to the memory address the end result is 4 bytes being overwritten in memory. Although it makes more sense to view the value as a float as opposed to an int, this does not mean its wrong to do it another way. Also depending on program/script you are using to read/write memory, it may be more convenient to treat the values as integers, or even a char array. Don't call him retarded when he gave an elegant explanation of why this hack works whether you treat the value as an integer or float, just the way the value is displayed is different. This is an important concept that many people here need to understand.

[Cypher]

Originally Posted by Etherea

Chazwazza, torn68 brings up a perfectly valid point and there is no reason to flame him. Whether you write a float, int or a char[4] to the memory address the end result is 4 bytes being overwritten in memory. Although it makes more sense to view the value as a float as opposed to an int, this does not mean its wrong to do it another way. Also depending on program/script you are using to read/write memory, it may be more convenient to treat the values as integers, or even a char array. Don't call him retarded when he gave an elegant explanation of why this hack works whether you treat the value as an integer or float, just the way the value is displayed is different. This is an important concept that many people here need to understand.

If you think he gave an "elegant explanation" you're just as stupid as he is.

[Etherea]

Originally Posted by Chazwazza

If you think he gave an "elegant explanation" you're just as stupid as he is.

He made the point he was trying to make, and there was nothing factually inaccurate in his remarks. There you go again with calling people stupid or retarded. Let's not be so quick to judge.