Performing maintenance on the server, shouldn't be terribly long but I make no promises. MCMyAdmin is taking more RAM than the server itself is, and it's not all that useful, so I'm trying to dump it for ZMA.

*does a tap dance*

*fails*

i love sandstone.

i just.

sand is USEFUL now!

i need to build a replica of luke's farm house. NOW! but, please, duh, make your time. the smoother the better.

Ok, I believe I got it all cleaned up. I ended up using a different wrapper than ZMA because ZMA was acting up. I ported everything over, so your game experience should be the same as before (if not better). PM with any problems and I'll do my best to fix them postehaste.


Oh, and a map.

So we are leaving the old world behind? Just asking as Whitty said he had backed it up and we wouldnt notice the change to the new system...

EDIT: Just reread the previous posts and saw Whitty say about the new map... its just that we had all built a lot of large things on the old map...

We can use the old one if yall want.

We can put it up to a vote.

Newmap newmap newmap newmap newmap.

I just came across lapis lazuli, whats the use for this stuff?

To look blue.

use it to die wool blue. You can also make blocks of it [like gold and silver]

Should you find the secret island known as Tear of Svalbard, please do not destroy it. That is my baby <3 I will, however, give you a cookie if you take a screenshot of it and post it up here.

EDIT: Also, minecraft.net appears to be down right now. Hopefully it'll get fixed soon.

You guys got any clue what 'Disconnect:Protocol Error' and/or 'Lost Connection:End of Stream' mean?

Problems with Minecraft.net. Just keep trying till you get in, maybe every five minutes or so.

If you want a more in-depth analysis, it seems that the server software verifies your username and password by sending your details to MC.net, then waiting for a response to the positive. The timeout on the serverside is much longer than the clientside timeout, so while it's waiting your client may time out and disconnect, but the server is not looking at that, so will continue waiting for MC.net to reply. If you reconnect while it's still waiting, the timeout of the server typically resets shortly after and disconnects you, giving you the end of stream error. As for the protocol error, it's probably somewhere in that mess as well.

Sounds like something that should be fixed STAT. Thanks for the explanation.

Add me.

Gah, PM me these things, it saves on clutter.