hack for 2.4.2

[unknow2k]

WallClimb hack for 2.4.2

Hex Edit:
005fbd1c 0f,85,47,01,00,00 -> e9,48,01,00,00,90

[unknow2k]

camera hack for 2.4.2

Hex Edit:
0068bfba 75 -> eb

[macintox]

nice, good job

[vivecs]

sweet job lol

[SCSI73rm1n8r]

WallClimb hack for 2.4.2

Hex Edit:
005fbd1c 0f,85,47,01,00,00 -> e9,48,01,00,00,90

I find difficulty jumping using this patch, and running up walls feels quite glitchy.
Instead, try this:
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 instead of altering the program flow and breaking other things.

[gunnleif1]

thanks, i need this one=)

[Poihtis]

very good job mate

[Therrm]

Keep crashing my wow

[zhaixz]

good job~!:wave::wave::wave:

[korknob]

used this earlier, had to set that memory segment to read and write access. within 3-4 minutes i got disconnected. when i tried to log back in it gave an error about 'cannot validate client. this may be caused by third party software... etc' i restarted wow and tried again but now the password has been changed. i dont have access to the email on that account so now im SOL. using MHS to edit the memory, never had any issues before doing that particular edit so in summary, watch out for editing RDATA and code segments, they're scanning it for changes.

[Xarg0]

If you do changes in the code segment, you need to revert them if you got dc'ed, because Blizzard Validates the WoW Client every time you logg in, this is mainly to protect you from Trojans and stuff like that.
If you changed some stuff inside RDATA you'll need to reset the page execute rights, or wow will crash some times...

[UnknOwned]

If you do changes in the code segment, you need to revert them if you got dc'ed, because Blizzard Validates the WoW Client every time you logg in, this is mainly to protect you from Trojans and stuff like that.
If you changed some stuff inside RDATA you'll need to reset the page execute rights, or wow will crash some times...

Or jump the check ^^

[kynox]

Just fyi, the offset you want to hook is 0x0086ADD0. Its called before the CRC check is executed. Your program flow would want to look like this:

void Hook() {
RemoveModifications();
CallOriginalHook() // 0086ADD0
ApplyModifiications();
}

[zeonlegend3]

nice unknow gd job

[zeonlegend3]

but i do prefer SCSI73rm1n8r's version better but +rep to both of ya