Yeah, I could never figure out exactly why it sends that move item packet like that. From what I recall, it counts down by 960 (IIRC) every time it comes in. I thought it started at the same value every time a client logged in, so they would had to be logged in for months for it to get below 3 billion. Since that was extremely unlikely, I just set it to that. Apparently it doesn't start at the same value each time and instead it sounds more like it is related to something like a unix timestamp.
I would prefer to figure out why it is being sent and handle it correctly, but since it doesn't break anything to ignore it, that should be ok for now.
Some of my thoughts on what it might be:
1. Maybe something related to food/drink consumption. Though, I kinda doubt this since food/drink is already handled in other packets just fine.
2. Could be some type of inventory check, that forces the server to make sure the client and server are in sync somehow.
I would like to see what Live sends when they get this packet. Maybe I have one in one of my packet collects somewhere. It would be interesting to see what a reply (if any) would be like.
Either way, that patch should work for now. We can get it on the SVN ASAP.
Last edited by trevius; 01-14-2011 at 04:59 AM..
|
Threaded Mode
