Player Profile packet
I'm goofing around a bit with sending the client the player profile structure and wondering if anyone might have any tips. In my testing, zone is sending it after it receives the zoneEntry opCode... followed closely by the zoneEntry, TimeOfDay and Weather packets.
Since I'm just goofing around with a little part of the mammoth profile struct there's maybe 20% that I leave blank. Problem is the client keeps disconnecting on me so it must not like something about it. I crc it and have made sure the struct length is 19568.
Anyone know anything to watch for here? Is there anything that absolutely HAS to be in the profile when zone first sends it to the client? Or do I perhaps have the order of things off? Thanks in advance.
|