[WoW] [5.4.7 18019] Release x86 Info Dump Thread

[charles420]

AuraCount1 = 0x1218,
AuraCount2 = 0xE18,
AuraTable1 = 0xE18,
AuraTable2 = 0xE1C,
AuraSize = 0x40,
AuraSpellId = 0x28,
AuraStack = 0x2D,
TimeLeft = 0x34,
OwnerGUID = 0x20,

[plaguedog32]

Awesome thanks! I guess those offsets hadnt changed since previous posts I had seen but the code I was basing mine off of needed the aura tables swapped to work correctly.

[Torpedoes]

I updated my original post ([WoW] [5.4.7 18019] Release x86 Info Dump Thread) to include a few other offsets as well as some corrections in case anybody's interested.

[xxspokiixx]

hey men thanks for all this work you've done .
Maybe is to much to ask but, can you help me with a pqr offset for the rpp server (the official test server for wow) :P??

[charles420]

Some new offsets im using for my new Bot figure ill post them

PetNumSpells = 0xDC2100,
PetSpellsPtr = 0xDC2104,
SpellBookNumSpells = 0xDC20F0,
SpellBookSpellsPtr = 0xDC20F4,
IsAutoRepeatingSpell = 0xC98C10,
MapLandmarkCount = 0xDC2CC8,
MapLandmarkInfoArray = 0xDC2CF4,

[redcatH]

ask for advice
how many Spell_C_HandleTerrainClick offset ？

[redcatH]

Seems to be 0x38F92D?
use 17399 Pattern~

[xalcon]

0x57C408 => bool __cdecl IsQuestComplete(int questId)
0xC8BE10 QuestCachePtr(?)
0xC8BE00 QuestCount

Was reversing Script_GetQuestsCompleted() for the last view hours and I think I actually understand whats going on
It looks like blizzard is sending all quests (even those unavailable to players) to the client, so GetQuestsCompleted no longer returns incomplete datasets.
There is a big array of structs @[0xC8BE10] with the size @0xC8BE00, something like

struct GlobalQuestListEntry
{
    int QuestId;
    int Unknown;
}

When GetQuestsCompleted() is called, it iterates over all quests and calls sub_57C408 for each quest id (I've named it IsQuestComplete :P)

[charles420]

ya quest was a fun one !!

[akspa420]

0x57C408 => bool __cdecl IsQuestComplete(int questId)
0xC8BE10 QuestCachePtr(?)
0xC8BE00 QuestCount

Was reversing Script_GetQuestsCompleted() for the last view hours and I think I actually understand whats going on
It looks like blizzard is sending all quests (even those unavailable to players) to the client, so GetQuestsCompleted no longer returns incomplete datasets.
There is a big array of structs @[0xC8BE10] with the size @0xC8BE00, something like

struct GlobalQuestListEntry
{
    int QuestId;
    int Unknown;
}

When GetQuestsCompleted() is called, it iterates over all quests and calls sub_57C408 for each quest id (I've named it IsQuestComplete :P)

Could a tool be made to extract all the possible quests from this struct (assuming that Warden isn't scanning that memory location,)?
Any speculation as to why they now issue the client with all the quest id's instead of the necessary id's?

[xalcon]

Could a tool be made to extract all the possible quests from this struct (assuming that Warden isn't scanning that memory location,)?
Any speculation as to why they now issue the client with all the quest id's instead of the necessary id's?

Ehm... what? Even if warden would scan this memory location.. it wouldnt have any impact since you dont write to it. (Your systems antivirus is scanning memory all the time, so why should blizzard be alarmed when some quest ids are getting scanned?)

I havn't looked into the other API functions but since quest data like title or text is not available until you talk to the questgiver, I dont think it might be possible to extract all quest data without actually doing all da quests!

[Ginsplosion]

In anticipation for 5.4.8 currently on the PTR and probably imminent does anyone have the offsets for PQR - Offsets: 18224?

Always have issues retrieving a few of the lines needed for the offset file, closest I get is about 75% and always manage to miss something.

[~Unknown~]

Anyone have a semi updated IDB file? I was just going to do a diff between an older one, but it seems all the filebeam links from every old IDB are broken.