Is there anywhere where there is a listing or db of info about the packets WoW sends/recieves?
Is there anywhere where there is a listing or db of info about the packets WoW sends/recieves?
There was once a project called WoWSniffer (or something similar) that had a listing of packets. Also, the Mangos/Antrix private server projects have enums of packets which should be more up to date.
Mangos has a fairly up to date list, I've used it in one of my packet-based projects.
Do I have to download the whole server to see these enums...?
Errr. Wrong enums lol.
He's looking for the packet based ones.
Because I'm nice *cough*, here they are.
https://mangos.svn.sourceforge.net/s...game/Opcodes.h
there is an opensource program made for mangos called pseuwow, it's something of a wow.exe replacement you can connect to servers through it.
you can probably dig through the source for any packet-related info you would ever need.
http://mangosclient.org
You can do the same with Mangos, and afaik Mangos has more information. Just check out the source file with the opcode handler table to grab the function of the opcode you're interested in.
The WCell project also has a very good repository of information on packet structure.
Am I correct with the way I'm getting process ID? It's giving me error code 6 between findwindow and getprocessid, invalid handle. I'm not sure what I'm doing wrong.
EDIT: Nevermind, I'll just use a C# injector =/Code:HANDLE hWow = FindWindow(NULL, "World of Warcraft"); DWORD pId = GetProcessId(hWow); ForceLibraryNow(pId, "...");
Last edited by lanman92; 09-27-2008 at 03:28 PM.
FindWindow returns a HWND, not a handle..
What returns a HANDLE then...? Do I like have to enumerate the windows and check the window name to get a HANDLE?
You can use GetWindowThreadProcessId(HWND windowhandle, LPDWORD lpdwProcessID) to get the PID by a WindowHandle retrived with FindWindow
I prefere doing a tlh32snapshot and walking the processlist until I found the one of WoW.exe (this shit is case sensitiv if you renenamed the WoW.exe to wOw.exe you wont find it bye searching for WoW.exe :>).
You'll need a PE32 structure for this, I've wrote a wrapper class for finding a process by exe name and some memoryreadwrite Stuff, yet the memoryreadwrite stuff isn't realy good but it's easy to use for process handling, you can use it if you want to, it's free since it's nothing tooo special and it looks a bit like the wowsharp.memoryreader class :-)
I hacked 127.0.0.1