I have the wow offset dumper, but he is outdated. I know that the descriptornames are removed since 400.
I have the wow offset dumper, but he is outdated. I know that the descriptornames are removed since 400.
/----- (004BC690) --------------------------------------------------------
void __cdecl sub_4BC690()
{
void *v0; // eax@2
if ( !dword_C1C980 )
{
v0 = sub_7A6F40(57752, (int)".\\FriendList.cpp", 1207, 0);
if ( v0 )
dword_C1C980 = sub_4B68E0(v0);
else
dword_C1C980 = 0;
sub_4B3B80(0x2FEDu, (int)sub_4BC370, 0);
sub_4B3B80(0x3B68u, (int)sub_4B69D0, 0);
sub_4B3B80(0xCBEBu, (int)sub_4B6A10, 0);
sub_4B3B80(0xBFECu, (int)sub_4BC350, 0);
sub_4B3B80(0x7FECu, (int)sub_4BC300, 0);
sub_5F9E60((int)"whois", (int)sub_4B78F0, 0, (int)"Ask the server to do an account/real name lookup on a character name");
That pretty ****ed up haha, looks like a decompile of assembly. Looks like we have the main function, that then creates a
pointer of type void (this will we need to be typecasted if you want to use it correctly, void doesn't have a Definied-Memory usage)
Then you have something about if its not double word, then continue. v0 now points to most likely a void function that
takes an integer, and then looks like another in a typecasted number?, and a couple of more integers.
then you have an if statement, and then an else, basicly looks like a check to see if v0 worked correctly.
Oh really?That pretty ****ed up haha, looks like a decompile of assembly.
Yes it can point to anything as long as its typecasted
At least 5 things were not correct.
That pretty ****ed up haha, looks like a decompile of assembly. Looks like we have the main function, that then creates a
pointer of type void (this will we need to be typecasted if you want to use it correctly, void doesn't have a Definied-Memory usage)
Then you have something about if its not double word, then continue. v0 now points to most likely a void function that
takes an integer, and then looks like another in a typecasted number?, and a couple of more integers.
then you have an if statement, and then an else, basicly looks like a check to see if v0 worked correctly.
Patch 4.0.0.12232
Cataclysm Beta realms going live, blizzard have extended maintance today
NO opcode changes in this patch again. Need only new updatefields.
And they have changeed the spell.dbc fields from 178 to 48 Oo
We will be performing extended maintenance on the realms listed below on wednesday, June 16th, beginning at 00:01 CEST. The maintenance is scheduled for 24 hours as we prepare for the upcoming expansion. These realms will be playable again at approximately 23:59 on wednesday, June 16th.
Last edited by doityourself; 06-16-2010 at 08:57 AM.
hmm haith
SMSG_COMPRESSED_MOVES = 0x49E0, // Haith
how you got this one cause the one i have, got a diferent opcode and acording to my research its correct. The weird thing is i got that one also before and i dont know how i got it lol.
Has anyone looked at build 12479 yet?
hmm yes. many opcodes have been changed again but not all opcodes.
I have changed some opcodes to fix stuck on connected and a few other opcode errors.
Commit f0e7182bebbab0bcb63b51882f1b1001182e5e4f to Fabi's diamondcore - GitHub
and I hope that this dbc fixes are right
http://github.com/Fabi/diamondcore/c...bd300f90aa924d
world entering need fix :P
maybe you can help to search some opcodes in 12539/12604 i both are the same. I have found some opcodes, but need a little help. hmm can't find SMSG_AUTH_CHALLENGE
---------- Post added at 11:26 PM ---------- Previous post was at 10:16 PM ----------
now 12644 :P same opcodes
I'm lazy as **** and I have other things to do that distract me from this, I'm not going to make promises anymore but I'll try to muster some motivation :|
By the way has anyone not in the beta got their hands on the new downloader yet? Because we're stuck with 12644 until then.
Found it: enUS WoW Patch Mirror
New installer for build 12635, then it should patch to build 12694 with the new downloader.