(10-23-2011, 05:09 AM)FakeTruth Wrote: 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
haha, I've been back and forth over http://mc.kev009.com/Protocol. I'm using that as a reference to try and add some protocols. I want to be able to get creative mode working like it should and go from there.
I've got a test server up at 199.167.133.105:11111
It's a 64 bit Ubuntu 10.04 server with 16 GB RAM and a Xeon Sandy Core E3-X1230 processor. MC-server is only using around 30 - 100 MBs though. Bukkit on the other hand is using about 3GB, but is holding onto 12GB.