OpCode names, where are they come from?

[dashja]

Yeah, the emu devs got them very early during the first beta or so.
The only build with opcode names I saw was a 4.0.0 build uploaded by namreeb.

Are there more 'secrret' builds with those names?

I know we have some emu devs like TOM_RUS here, maybe they know more about it.

Thanks.

[daCoder]

Look at http://www.ownedcore.com/forums/worl...lease-ptr.html ([WoW] Binary Collection (Release & PTR))

There are some binaries from the beta or PTR with debug information.

[dashja]

Hey, thanks for the reply.

Yeah I know those debug builds, but they don't have any opcode names, just function and struct informations etc.
Never saw any build with opcode information except 4.0.0.

I'm talking about the packets like CMSG_... SMSG_....

Just wondering, cus after 4.0.0 got leaked by namreeb somehow, i checked some emu sources and all the opcode names in the emus were correct.

edit:

After I browsed the forums, i found out that the wotlk beta build 8885 has some more information.
And indeed, that build has also opcodes names. So I guess there're many more builds. A complete list would be very great.

[namreeb]

Yeah, the emu devs got them very early during the first beta or so.
The only build with opcode names I saw was a 4.0.0 build uploaded by namreeb.

Are there more 'secrret' builds with those names?

I know we have some emu devs like TOM_RUS here, maybe they know more about it.

Thanks.

That particular binary was from before the friends and family opened, and it was meant to be internal.

[dashja]

That particular binary was from before the friends and family opened, and it was meant to be internal.

The question is why they make the same mistakes again and again? I mean it's a 1-2 minute job to check the builds before they put them on the download servers.
Implementing jam mesages and randomizing the opcodes is just waste of time.

[xalcon]

The question is why they make the same mistakes again and again? I mean it's a 1-2 minute job to check the builds before they put them on the download servers.
Implementing jam mesages and randomizing the opcodes is just waste of time.

Have you ever worked in an environment like the WoW Developers? Sometimes there is so much going on, that you just forget some stuff. Sure, there are ways to prevent such mistakes, like adding a automated check of the executables to their workflow, but I think the workflow is actually quite heavy.
Why do big/important companies get hacked via simple stuff like sql injections? I think you can answer that by yourself

[namreeb]

Have you ever worked in an environment like the WoW Developers? Sometimes there is so much going on, that you just forget some stuff. Sure, there are ways to prevent such mistakes, like adding a automated check of the executables to their workflow, but I think the workflow is actually quite heavy.
Why do big/important companies get hacked via simple stuff like sql injections? I think you can answer that by yourself

Also in this case the binary was something that was never meant to see the public eye. I imagine the workflow is much simpler in this case.

[Tanaris4]

Everything is labelled in the mac 5.0.1 15662 build as well

[dashja]

Everything is labelled in the mac 5.0.1 15662 build as well

Yeah it is, but no opcode names : (
I'm pretty sure there is a more up2date opcode build as the wotlk build.

It's just hard to find it if you have to look into every binary, cus to get the most binarys i have to install older WoW beta/ptr versions.

So a little hint from the emu experts would be very great :*

[doityourself]

yea there are no opcode names, but you can use the function names for them...

[Bananenbrot]

Everything is labelled in the mac 5.0.1 15662 build as well

Awesome... didn't know that!

[dashja]

yea there are no opcode names, but you can use the function names for them...

But that's not my goal ; ) I want to have an opcode dump and don't copy paste anything out of the emu sources.

[Frosttall]

But that's not my goal ; ) I want to have an opcode dump and don't copy paste anything out of the emu sources.

Use the leaked debug infos?!

Sent from my GT-I9100 using Tapatalk 2

[doityourself]

this is what I said^^

[dashja]

And I said I want the opcode names (also the cheat opcodes which have no functions), not the function names.
I don't want the random opcode values, just their original names.