Player Profile packet

[EvoZak]

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.

[AndMetal]

In the interests of possibly a simpler solution than just updating the entire profile, what exactly are you trying to change?

I was under the impression (without confirmation, so I could be wrong) that the profile was basically sent during zone in, and then everything in the profile was just updated while in the zone on both the server & client sides using different packets. In other words, the profile is the starting values for everything in memory, and everything gets poked & prodded. This also explains why, if you change the profile while the character is logged in, it won't send to the client normally, it will be overwritten by whatever is in server memory for the client, but it works fine if you make the change when the character is offline.

Also, how are you trying to send the profile packet to the client (maybe a code snippet)? Maybe there's a Kick() function mixed somewhere in there (like when you change a class, race, etc, for it to take effect)?

[EvoZak]

I'm just experimenting with different sections of the profile. It's actually at zone in where I'm playing at. I'm not filing the entire struct, I've just sort of stubbed out about 80% of it give or take. Reason: I don't want to go through all the LDON, tribute, etc. parts since I won't be using them.

I was just wondering if anyone knew if it is an absolute necessity to fill the entire struct. Essentially the client biffs it on me and I'm thinking maybe that is why.

[KLS]

mmm I dunno what happens if you send a pp packet out of order, I'm guessing it probably thinks the data stream is corrupt and drops you. Not filling it fully probably isn't an issue unless it's a key piece of info in which case it might also drop the client cause it thinks the data can't possibly be right.

[EvoZak]

Originally Posted by KLS

mmm I dunno what happens if you send a pp packet out of order, I'm guessing it probably thinks the data stream is corrupt and drops you. Not filling it fully probably isn't an issue unless it's a key piece of info in which case it might also drop the client cause it thinks the data can't possibly be right.

Yeah out of order shouldn't be the issue (hopefully) as it looks like the very first application packet sent by zone. Or is there something that comes first? To me it looks like after zone gets a zone entry OpCode it sends back the profile first thing.

Anyways thanks for the input, I just thought I'd shoot it out there in case someone knew something like "oh yeah, if you don't have field x filled in the client will disconnect".