the server we are currently playing on is private.

But i think our main server, discovr.us, is already updated too. Try this one.

Weird, on that server, everything works perfectly fine. I don't know whether that issue was caused server-side or client-side, but I've played for 15 minutes now, editing blocks like a lunatic and not one single timeout.

Let's just hope everything works out fine on Michael's server too. As soon as the server is up again, of course.

Aw, now I can't play anymore . Auto update .

Minecraft is a perfect example why auto-updates are sometimes really really freaking bad.

Yep, I wish I could just keep the old version, instead of it auto-updating whether I want to or not.

You can start a new world for fun and set back the old world when mod updates are out.

What were these mods for, anyway?

edit: nevermind, just found a description for hmod.

Preventing the world getting utterly griefed

A tip, i just discovered this - When you use a patcher like the one that enables 32x32 textures (i think its called HD Patcher), then it patches minecraft back to 1.2.2 but won't update when you start it again.

There is a version file in the directory where the minecraft.jar is, maybe it is easy to change it to 1.2.3 too and keep the old client if you still have? I haven't opened it yet.

Server is up again, but don't attack sheep. If you do, you will only do minuscule damage after that (i.e. 10 hits to kill a chicken).

You will die after your first login, just disconnect and reconnect, then everything should be back to normal.

Monsters are disabled temporarily, wanna see how (un)stable this new update is first.