TWiTCraft Server bork?

[Timberwolf1777]

I just read the post on connection problems for other players. This issue actually started around 2:30AM PST early this morning. There were three of us on at the time and we all got kicked (Internal exception: java.net.SocketTimeoutExceptionand: Read timed out) then the server was unreachable from the multiplayer login screen. I tried off and on for an hour then went to bed . Sorry curley, I dont twitter. Even though the server has been rebooted, when I just tried to login just now (1:45 PM PST) again (it said 17 people were on it), I got a severly lagged connection and got kicked again promptly. The dynamap is flukey and sometimes loads and sometimes doesnt. No players are appearing on it. Maybe all 17 got kicked too?

Thats it. Thanks for looking in to this Curley!

[Timberwolf1777]

Ok so the server was crashing thanks to me .... my location actually. There must be a very bad chunk at or near x:342, z:4420. (Curley thats not exact but thats the little beach i kept loading near.) My location is fixed now so no more crashing! Just stay far from that chunk!

[Curley]

Thanks for the write up timber.

I looked back in the logs from last night and you're right, the crash from "this morning" was the same we had today when you tried to come back into game. So as timber said, stay away from that chunk till i can get to my home computer and get in game to experiment.

In addition to that chunk when timber logged in that section the chunk loading method crashed and complained that these chunks (x14, z280 - x31, z269) were corrupted as well as this x343, z430. While this all just may be a simple chunk load bug that has fixed itself I'm asking everyone to please just avoid those chunks for now until I can be around to fix and verify. I'll post here with updates I find. kthxbai.