WoW Current Statics and Offsets

[localhostage]

Target base, from target base -0x8 + 0x{HPOffset}, you can't find trough the player his target hp, you need to do it from the mob itself.

ttt, i've been searching for the target base and came to no luck, also tried searching for forums. have you found a method to locating the target base?

or for that matter, has anyone else?

i'm pretty close to writing a full on WoW Class Library in .Net and this would really take the cake.

[suicidity]

Hey Froogle, thanks for the reply! I see my error now and what I did was just one of those coding.. gotchas!

I was doing 0xA698000 + 0xA548 which came out totally wrong.

Just want to note to anyone else who ran into this issue that 0xA698000 is not the same as A698000. lol, thanks!

Yes it is, You have to subtract the player-base from 0xA548 though. You should be adding 0x2548 (0xA548 - 0x8000, player-base is 0x8000).

You subtract 0x8000 (or &H8000 for .net apps) so you always replicate the 0xA548 ending. 0x2548 is the true offset, and you must subtract 0x8000 from all the endings provided that have 4 or more digits (because the fourth digit falls on the 8 in 0x8000).

-Suicidity

[Froogle]

Yes it is, You have to subtract the player-base from 0xA548 though. You should be adding 0x2548 (0xA548 - 0x8000, player-base is 0x8000).

You subtract 0x8000 (or &H8000 for .net apps) so you always replicate the 0xA548 ending. 0x2548 is the true offset, and you must subtract 0x8000 from all the endings provided that have 4 or more digits (because the fourth digit falls on the 8 in 0x8000).

-Suicidity

Your post makes perfect sense and I messed up with my math . . . I'll add a note on that offset.

[suicidity]

all the 4 digit offsets posted require to be subtracted by 0x8000

same with another post about the player structure, You must subtract each offset by 0x10 because of the true offsets and structure

[raindog]

man, you guys are going about it all wrong! There is a function that has been described in a different that when passed a GUID it will return a pointer to the object with that id. In the case of the current target, it works something like this:

WowObject *p_targ = GetObjPtr(player->target);

[Gothian]

man, you guys are going about it all wrong! There is a function that has been described in a different that when passed a GUID it will return a pointer to the object with that id. In the case of the current target, it works something like this:

WowObject *p_targ = GetObjPtr(player->target);

What are we supposed to do to get that to work? Were not a leet as you

[localhostage]

Yes, what do we do what that? 'player -> target' ??? Is there a method which uses the player ptr to get target ptr? Then do I just do player +health offset to the target offset?

[schlumpf]

Its called C++... player->target is just a fukken pointer.. Your object player has a structure containing that target variable. The function GetObjPtr(); returns a pointer on a WowObject. The WowObject p_targ will be a pointer to that target's structure then.

Learn C.

[Gothian]

Its called C++... player->target is just a fukken pointer.. Your object player has a structure containing that target variable. The function GetObjPtr(); returns a pointer on a WowObject. The WowObject p_targ will be a pointer to that target's structure then.

Learn C.

Ahh I see, I though it was some sort of machine code, I didnt know it was simply C, which means I can do a .NET version

[suicidity]

..... jesus christ. Shoot me now. lol j/k j/k

[robotkid]

excellent post! i saved some hours of memory searching =P +rep

[raindog]

Ahh I see, I though it was some sort of machine code, I didnt know it was simply C, which means I can do a .NET version

In this case you can't really. GetObjPtr is a function inside of wow. I defined a structure that conforms to the same struct wow has. You can't really do that in .NET, perhaps unsafe C# but not VB.

[Gothian]

In this case you can't really. GetObjPtr is a function inside of wow. I defined a structure that conforms to the same struct wow has. You can't really do that in .NET, perhaps unsafe C# but not VB.

You logic is flawed here as C# and VB.NET are essentially the same language.

You can take C# code and translate it into VB.NET and it will have the exact same functionality. It all compiles into IL code anyway.

[Cypher]

You logic is flawed here as C# and VB.NET are essentially the same language.

You can take C# code and translate it into VB.NET and it will have the exact same functionality. It all compiles into IL code anyway.

WRONG! (Sorry, but you are )

VB.NET does NOT have an equivalent of the 'unsafe' keyword, you need to add a C# part to your solution to do the 'dirty work'. Unsafe C# code is run as native code and does not run under the CLR.

Links:
O'Reilly Media | C# & VB.NET Conversion Pocket Reference
Choosing between C# and VB.NET
Philippe Lacoude Homepage
Comparison of C sharp and Visual Basic .NET - Wikipedia, the free encyclopedia

[Gothian]

WRONG! (Sorry, but you are )

VB.NET does NOT have an equivalent of the 'unsafe' keyword, you need to add a C# part to your solution to do the 'dirty work'. Unsafe C# code is run as native code and does not run under the CLR.

Links:
O'Reilly Media | C# & VB.NET Conversion Pocket Reference
Choosing between C# and VB.NET
Philippe Lacoude Homepage
Comparison of C sharp and Visual Basic .NET - Wikipedia, the free encyclopedia

Consider myself proven wrong.

But in my defense, I was not aware of the "Unsafe" feature, because what you can do with C#, you can do with VB.NET (besides the unsafe portion of course)

But my guess is that you can use the Windows API calls to manage that? Or just write a DLL and reference it in a .NET application?