[WoW][4.3.0.15005] Info Dump Thread

[miceiken]

IsIndoors checks are server side :P

I think you wont be able to mount up inside but its easy to stay on your mount ;D

I'm pretty sure he's aware of that, and is looking for a work-around...

[Require]

Sorry for being a complete newbie, but how do you gain offsets for lets say the player's health? Because I'm not able to find those in the dump

[ccKep]

Sorry for being a complete newbie, but how do you gain offsets for lets say the player's health? Because I'm not able to find those in the dump

You could atleast TRY:

CurMgrPointer = 0x009BE678, //4.3.0.15005
CurMgrOffset = 0x463C, //4.3.0.15005
NextObject = 0x3C, //4.3.0.15005
FirstObject = 0xC0, //4.3.0.15005
LocalGUID = 0xC8 //4.3.0.15005
...

public enum WowUnitFields
{
...
UNIT_FIELD_HEALTH = 0x20 + 0x48,
...
UNIT_FIELD_MAXHEALTH = 0x20 + 0x60,
...
};

Before endless QQ IT DUN BROKED posts.

Descriptors are now at 0xC instead of 0x8.

Alternatively:

Playerbase:

PlayerBasePointer = 0x00A70AE0
PlayerBaseOffset1 = 0x38
PlayerBaseOffset2 = 0x24
Descriptor Offset = 0xC

Those quotes are from the first 2 pages, they contain ALL the info you need...

[Require]

@ccKep: Thanks, trying to find my way around here and I'll give that stuff a try!

hmm after trying for a while I came to the following: uint playerbase = BMagic.ReadUInt(BMagic.ReadUInt(BMagic.ReadUInt(0x00A70AE0) + 0x3 + 0x24);
I am getting an exception: ReadUINT failed.. which offset am I doing wrong or am I missing? Descriptor isn't needed for getting the playerbase like this right

EDIT: Correct me if I am wrong, but aren't we on 15050 at the moment?

[Thongs]

@ccKep: Thanks, trying to find my way around here and I'll give that stuff a try!

hmm after trying for a while I came to the following: uint playerbase = BMagic.ReadUInt(BMagic.ReadUInt(BMagic.ReadUInt(0x00A70AE0) + 0x3 + 0x24);
I am getting an exception: ReadUINT failed.. which offset am I doing wrong or am I missing? Descriptor isn't needed for getting the playerbase like this right

EDIT: Correct me if I am wrong, but aren't we on 15050 at the moment?

I haven't looked at your offsets, so they could also be wrong, but you need to add WoW's baseaddress to the 0x00A70AE0.
http://www.ownedcore.com/forums/worl...r-enabled.html (Finding the BaseAddress when ASLR is enabled)

[Require]

I haven't looked at your offsets, so they could also be wrong, but you need to add WoW's baseaddress to the 0x00A70AE0.
http://www.ownedcore.com/forums/worl...r-enabled.html (Finding the BaseAddress when ASLR is enabled)

Thongs, thanks for your help
I got an int back using this:

IntPtr baseWow = wow.MainModule.BaseAddress;
uint test = ((uint)baseWow + 0x00A70AE0);

I will check tomorrow if it worked by getting the player's level. Thanks so far!

[Fredi83]

EDIT: Correct me if I am wrong, but aren't we on 15050 at the moment?

Yep, but it shouldn't change much since it was a small hotfix for 15005.

[xalcon]

There are dozens of statics which hold the current map ID... why? O.o" I'm a bit confused...
anyway, some candy for you:

MapID = Wow.exe+0x8C8C9C
AnotherMapID_static = Wow.exe+0x8A26B0 // Is set to a realy high value (uint.Max?) when entering the character screen
loadingMapID = Wow.exe+0x897608 // Map ID of the map you are moving to (loading screen)

[Require]

Guys, I am having a problem that 2 of the same Guid objects are trying to be added to my list. Also, when I run my object manager it isn't able to find an object that compares to my localGuid (so it's the localPlayer).. I think I'm messing up some offsets:
private const uint staticClientConnection = 0x009BE678, // client connection, same address every boot
objectManagerOffset = 0x463C, // offset from the ClientConnection to the object manager
localGuidOffset = 0xC8, // offset from the object manager to the local guid
firstObjectOffset = 0xC0, // offset from the object manager to the first object
nextObjectOffset = 0x3C; // offset from one object to the next

I know that the first one COULD be wrong, but after double check the others should be fine.. Does anyone know whats going on?

[xalcon]

@require: this thread is for offsets and not for asking noobish questions

back2topic:
These offsets are needed for elevators and other transport objects (see http://www.ownedcore.com/forums/worl...detection.html (Elevator detection) for more info)
GameobjectX2 => objBase + 0x200
GameobjectY2 => objBase + 0x204
GameobjectX2 => objBase + 0x208
PlayerTransportGUID: wow.exe + 0xA70AC8

[zys924]

Long time haven't seen such offset posted, useful when setting values in Lua tables.
FrameScript::SetTable: Offset=0x2C650, IDA=0x42C650.

[vitecp]

can be deleted

[-Ryuk-]

Just a quick not to say that Warden has been updated.

So far I only have one new scan that was detected by our public bot(HeliosBots IS safe from this address).

Address: 0x4FA3E5 Bytes: 52 57 8B 7D F8 E8 81 E3 FE FF

Warden also seems to be idle at the moment(EU) and therefore I don't know if there are any other new scans.

[Weird0]

according to a froum post from a random user on the german forums this has been added, i dont know if that is any reliable source or if the user is just full of bullpoop ima go and post this here anyway since maybe it can help if it does then im glad i could have been of some help if not well just ignore this post ^^


Offset -- Length -- Bytes
0x704430 -- 9 -- 85 139 236 81 83 86 139 117 8
0x4FA3E5 -- A -- 82 87 139 125 248 232 129 227 254 255
0x621E50 -- 5 -- 117 62 246 70 60
0x1D9711 -- 4 -- 116 28 139 6
0x38ABBD -- 5 -- 116 40 139 77 24
0x44A6 -- 5 -- 232 133 239 63 0
0x1D970F -- 4 -- 133 219 116 28

/edit

Warden also seems to be idle at the moment(EU) and therefore I don't know if there are any other new scans.

does that mean its dorment and not doing anything right now or just that it is still scanning but not taking any actions right now ?

[-Ryuk-]

It's not idle anymore... But when I said it was idle I meant that the module was being pushed out but no scan data/requests were sent with it.