But there are more people who knows SOMETHING about things like that. I guess no more than 4-5 people here can at least understand what's included in that structure. And same: no more than 10 people here know, what the f... is struct and what language it is.
The language is C++ and a struct is a data structure which basically means a bunch of things grouped together as members and each member has its own length and type.
In the above code Soly posted, the struct is being declared as "MSG_CTRL_MONSTER_SPAWN" and has a series of elements grouped inside of it. The elements look like the header which means it is visible to the other .cpp files using it and then a series of types.
So we are declaring a struct called "MSG_CTRL_MONSTER_SPAWN" and the variables are listed under as short, float and char.
This snippet looks like you are spawning a mob using the variable (members) by including the char name, the type of mob and then the id of the mobs but don't hold me on that.
it also could be C imo.
And I didn't tell YOU can't understand, but only a few can do it.
Don't forget about 'fX' and 'fZ' variables. I guess these are coords.
What's more interesting for people who don't run their own server will be the actual packet with this message, so it could be injected That way if someone has a table with mob IDs, he can spawn himself whatever he likes
What's more interesting for people who don't run their own server will be the actual packet with this message, so it could be injected That way if someone has a table with mob IDs, he can spawn himself whatever he likes
Mob's ID is easy to get .
but i doubt any one but few can build a packet out of this code.
this code is just a tip on how to build a Mob spawn packet but rest of the job depends on packet analyzing, how 9Dragons packet structure looks like
but i doubt any one but few can build a packet out of this code.
this code is just a tip on how to build a Mob spawn packet but rest of the job depends on packet analyzing, how 9Dragons packet structure looks like
You won't build a packet from scratch. I used to have tons of material collected back when I made my injector. The only thing to be aware is the command counter. Else one can get most of the packets easily (wireshark is the easiest method) and using something like a middle-server can duplicate and inject them. Problem is that most of the time one gets DC, because of the collision with packets sent and expected from the server.