Unknown GroupSpawn Packet

07/13/2011 19:19 lesderid#16
Quote:
Originally Posted by sarkoplata View Post
elite sro is soooo crowded that i cant try as i spawn somewhere tons of 3019 packet coming :(
So make it so your bot is able to parse it even if they are in the same groupspawn packet?
No reason not to make it possible.
07/13/2011 20:12 sarkoplata#17
Quote:
Originally Posted by lesderid View Post
So make it so your bot is able to parse it even if they are in the same groupspawn packet?
No reason not to make it possible.
if it was impossible , no bots would be created ^^
Well of course that is my point to success but i need to analyze the structure before ^^
Here the teleporter id's from pk2 if anyone needs.
07/13/2011 22:33 lesderid#18
Quote:
Originally Posted by sarkoplata View Post
if it was impossible , no bots would be created ^^
Well of course that is my point to success but i need to analyze the structure before ^^
Here the teleporter id's from pk2 if anyone needs.
Never said it's impossible.
Anyways, you should just parse groupspawn EXACTLY the same as singlespawn.
I just call the singlespawn function from my groupspawndata function and it works great.
07/14/2011 13:30 sarkoplata#19
Quote:
Originally Posted by lesderid View Post
Never said it's impossible.
Anyways, you should just parse groupspawn EXACTLY the same as singlespawn.
I just call the singlespawn function from my groupspawndata function and it works great.
Well , looked to packets for hours and i just caught a packet includes NPC + PLAYER.
Got to parse it now :P
07/14/2011 23:14 ufonose#20
Quote:
Originally Posted by sarkoplata View Post
last question : are npc or teleport packets coming together with mobs or players etc? ( in groupspawn )
every object can be in there, buildings, teleports, flags, pets, npcs, players and mobs.
02/21/2012 21:11 vutle#21
Hey guys sorry to jump in 2 years later.

Is silkroad buffer at 4096 bytes length?

I've parsed 3019 group spawn packet but sometimes there are 43 stall players in one place.
This makes the buffer > 4096, so silkroad server split the packet out to two buffers.
This means that the second buffer are not in any order.
Do I have to join what ever is left over on the first buffer with the second one to continue parsing?
I'm using the simplex_proxy and have increased the buffer > 8192. But that doesn't increase the bytes received.

Thanks

- -.
02/21/2012 21:30 vorosmihaly#22
well,as far as I know,you just have to read all the packets with opcode 0x3019 until you receive groupspawn end packet :)
so you don't have to increase the buffer's size.
02/22/2012 20:11 paxemuman#23
Quote:
Originally Posted by vutle View Post
Hey guys sorry to jump in 2 years later.

Is silkroad buffer at 4096 bytes length?

I've parsed 3019 group spawn packet but sometimes there are 43 stall players in one place.
This makes the buffer > 4096, so silkroad server split the packet out to two buffers.
This means that the second buffer are not in any order.
Do I have to join what ever is left over on the first buffer with the second one to continue parsing?
I'm using the simplex_proxy and have increased the buffer > 8192. But that doesn't increase the bytes received.

Thanks

- -.
Don't try increase buffer size because data will be randomly trunkated sometimes(i have tryed), its possible to increase max bytes received but its temporary(windows set it by himself) and makes many problems, there is DLL to do this.
02/24/2012 22:30 vutle#24
Thanks paxemuman, I've resolved the problem a few days ago by merging the 3019 packet bytes.
Now I'm in the process of making loop script.
Looks like it's hard, I just got disconnected when try to buy potion from NPC :).
08/31/2012 01:15 sarkoplata#25
Quote:
Originally Posted by vutle View Post
Thanks paxemuman, I've resolved the problem a few days ago by merging the 3019 packet bytes.
Now I'm in the process of making loop script.
Looks like it's hard, I just got disconnected when try to buy potion from NPC :).
Use drew's api and you'll never have to think again about such stuff :) (sorry for bumping my own old thread)