10-23-2011, 05:09 AM
It's really difficult to find out what's causing the client to bitch about certain things (sudden disconnects or crashes, the client is incredibly unstable).
Whenever this happens I put breakpoints in the code after certain packets have been sent, like the login procedure, or wherever you suspect something is going wrong. You can also just disconnect the client after sending a certain packet to find out which packet exactly is screwing things up. Once you find the packet, you investigate if the packet is up to date and sending the correct data. If it's out of date, you update the packet according to this page http://mc.kev009.com/Protocol If it's up to date, you log all the data you're sending out and check if it is what you expect it to be, if not, find out wtf is going on
Whenever this happens I put breakpoints in the code after certain packets have been sent, like the login procedure, or wherever you suspect something is going wrong. You can also just disconnect the client after sending a certain packet to find out which packet exactly is screwing things up. Once you find the packet, you investigate if the packet is up to date and sending the correct data. If it's out of date, you update the packet according to this page http://mc.kev009.com/Protocol If it's up to date, you log all the data you're sending out and check if it is what you expect it to be, if not, find out wtf is going on