3.0.8 Addresses , Few useful things :)

[Soul_Curve]

Hey guys, Im new here. I program in C++ and AutoIT.. And I figured I post a few 3.0.8 addresses that are useful to those who dont know ASM yet and want to make a few hacks Hope you guys enjoy!

////Patch Day 3.0.8 Addresses! 
Player_Base = 0x127E13C
Fall Speed = 0x100BD40
Inf Jump Patch = 0x008D7768
Gravity = 0x96D168
Mountain Climb = 0x971F70

+0x89C -Height (Set -2 for Fly hack :)
+7D0 -X Coord
+7D4 -Y Coord
+7D8 -Z Coord

Set Inf Jump patch to "0x0075" or "0x9090" at 2 bytes , I love inf Jump :)

Also, I found this address: 0x92F984 and if you change the value to "4" it deletes the whole ground and all buildings, but it also deletes the UI.. It makes a noclip as well and all NPC's/Mobs start falling lol

I know its some simple stuff but ive made some great hacks with these! So if youd like post some of your findings here too! Nice to meet you all btw

[luciferc]

I will try that out. Cool though .

+rep since ur a leecher

btw i think gravity is watched thu not sure XD

[lanman92]

Are those all undetected? I know that the M2/WMO offsets are undetected, but I thought some of those others were watched by the server. A while back I tried reversing the beefy part of Warden that scanned all of the offsets that are really used a lot(SendPacket, Grav, etc.). Just curious if they are detected now.

[DrakeFish]

Thx for those arigity

Looks like I'm gonna post some too

Time Minutes : 12dae20
Time Hours: 12dae24
Time Speed: 12DAE4C

[Xarg0]

Are those all undetected? I know that the M2/WMO offsets are undetected, but I thought some of those others were watched by the server. A while back I tried reversing the beefy part of Warden that scanned all of the offsets that are really used a lot(SendPacket, Grav, etc.). Just curious if they are detected now.

Dude I'm pretty shure I already told you how to easily check if a certain offset is watched by warden, place a hardwarebreakpoint on read/access there and see if something pop's up that looks like warden ^^
This should atleast prevent you from getting insta banned and I do heavily recommand you to only use hardware breakpoints to check an offset for warden scanns, because memory breakpoints would cause changes to a CRC performed on that memory region.

[DrakeFish]

Also, I found this address: 0x92F984 and if you change the value to "4" it deletes the whole ground and all buildings, but it also deletes the UI.. It makes a noclip as well and all NPC's/Mobs start falling lol

If you try with a high value such as 1000000 you can see everything but buildings are shadows and theres a noclip

[Soul_Curve]

I will try that out. Cool though .

+rep since ur a leecher

btw i think gravity is watched thu not sure XD

No prob luciferc! , Im gonna release some more findings aswell! And a free open source hack or two... Cant wait to see your project

[lanman92]

I know how to check, I didn't have access to WoW or even IDA when I posted that so I just asked.

[arigity]

theres more then one way to skin a cat. if your worried about warden catching you then modify another spot.

[Cypher]

theres more then one way to skin a cat. if your worried about warden catching you then modify another spot.

Actually, if you were really worried about warden catching you then you wouldn't modify ANY read-only memory. It would take very little work for blizzard to just start hashing the entire .text and .rdata sections. It would be a welcome change too imo.

Or, if you were running on a single-core machine (ie probably a VM) you could write yourself a memory-cloaking driver. Although there are still ways to detect stuff like that they're highly technical and specialized and probably could never be implemented safely in a generic form, so if you're private I wouldn't worry too much.

[arigity]

Actually, if you were really worried about warden catching you then you wouldn't modify ANY read-only memory. It would take very little work for blizzard to just start hashing the entire .text and .rdata sections. It would be a welcome change too imo.

if you were that were about warden you really ought not to be in the memory editing section. theirs always a chance blizzard will add a handy-dandy new feature that catches lolhax but not doing something because they might add something new is stupid, their are retardedly large amounts of ways that they could implement new anti-cheating stuff.

[Cypher]

if you were that were about warden you really ought not to be in the memory editing section. theirs always a chance blizzard will add a handy-dandy new feature that catches lolhax but not doing something because they might add something new is stupid, their are retardedly large amounts of ways that they could implement new anti-cheating stuff.

Wow.. That is astoundingly ignorant.

First of all, this section doesn't just cover modifying read only memory, it also covers documentation of structs, functions, lua stuff, etc. basically WoW reversing in general, so leave the "this section is for memory editing" bs at the door because that's just stupid. (Also, last time I checked I said read-only memory. Memory in the .data section or on the heap would be next to impossible to police generically so I see no real problem in modifying that)

Blizzard already hash certain sections of memory to look for specific hacks, it would take VERY little effort to implement hashing of the entire .text and .rdata sections, and because of the nature of Warden 99.99% of the people modifying read-only data would get banned (yourself included). When you're dealing with code that can change in any way at any time with no 100% foolproof way to catch it thats something I'd definitely worry about, the fact you think that just because its not implemented currently means you should just ignore it as a threat is retarded.

Blizzard have been known to push Warden updates without warning, mid patch, just to screw certain cheats. Also, over Warden's life features to catch cheaters have both been added and removed (again with zero warning).

You're not dealing with static code here like that in WoW.exe that you can analyze each patch and be sure that its not going to change until the next patch, you're dealing with code that is highly volatile and can change whenever Blizz feel like it. I'll state it again, Warden gets updated regularly so you need to try and stay one step ahead, if you don't then sooner or later you're gonna get burned.

Also, I'd love for you to outline some of these "retardedly large" ways. The primary ways I see them adding better generic (generic being the key) cheat detection are:
* Stack traces (catching unknown threads or modules calling client functions)
* Read-only memory hashing (catching client hooks or constant mods)

Given Warden's history I would say that most other techniques such as scanning out-of-process, running in ring0, doing more aggressive API hook checks, etc would be too invasive for Blizzard to implement.

Furthermore, recently Blizzard seem to have become a lot more aggressive in policing cheats and hacks. As the saying goes, "better safe than sorry".

[Robske]

Haven't seen it posted yet so:
Target GUID is now at 0x10A58E0.

http://www.mmowned.com/forums/wow-me...-0-8-more.html

^^

fillar

[arigity]

theres more to the memory editing section then covering read-only memory? thanks for that sherlock i wasn't aware. if your paranoia of warden is so great that you feel you'd be better off entirely ignoring read-only modifications based on the idea that they *might* add something new then you simply shouldn't bother.


worry about it when it does happen not whether its going to.

[Gamer]

http://www.mmowned.com/forums/wow-me...-0-8-more.html

^^

fillar

Searched for 0x10A58E0 and it was written as 0x010A58E0 xD

Sorry about that, deleted.