-
7.3.2.25549
7.3.2.25549 x86
Code:
LocalPlayerName: 0x01368F58
LocalPlayerGUID: 0x01368F48
ObjectMgr: 0x114FD7C
First: 0x0C
Next: 0x44
Type: 0x10
GUID: 0x30
PlayerX: 0xAE8
PlayerY: 0xAE8 +0x04
PlayerZ: 0xAE8 + 0x08
PlayerLevel: 0x4AC0
CameraBase = 0x12CD614
CameraOffset = 0x0324C
CameraOrigin = 0x08
CameraMatrixX = 0x14
CameraMatrixY = 0x14 + 0x0C
CameraMatrixZ = 0x14 + 0x0C + 0x0C
CameraFov = 0x38
NOTE: to run wow 32bit these days, you have to call wow.exe with the following parm: '-noautolaunch64bit', i am pretty sure there was also an option that allows you to use the battle.net auto login, but i forgot that one , example of usage:
Filename: Startwow.bat
Code:
echo Starting wow 32bit
"Wow.exe" --noautolaunch64bit
pause
Have fun!
Last edited by MrNoble; 01-03-2018 at 09:24 AM.
Any fool can write code that a computer can understand. good programmers write code that humans can understand.
-
Post Thanks / Like - 1 Thanks
pogob (1 members gave Thanks to MrNoble for this useful post)
-
Whats up with the chat Position?
i guess its here: 0x12864C8
Most of the time its ChatBuffer - 0x04, ChatBuffer is 0x12867B8 so the ChatPosition shold be 0x12867B4?
The value is static so that doesn't seem to be working, the other one close to it keep increasing when chat message is added, but instead of going to 0 or 1 after hitting 60, it keeps going up.
The max value i got before the game crashed was 210+, anyone else noticed some weird changes?
Any fool can write code that a computer can understand. good programmers write code that humans can understand.
-
Fixed it, found the correct ChatPosition at: 0x12E0218
Seems like the position is now located at the end of the chat thingy, The chat buffer is 60 long.
And the chat buffer starts at 0x12867B8 while each message is 0x17E8 long.
0x17E8 * 60 = 0x59A60,
ChatBuffer 0x12867B8 + 0x59A60 = 0x12E0218
Any fool can write code that a computer can understand. good programmers write code that humans can understand.