tabacco

Looks like another piston issue is breaking the server (somehow causing an unhandled ArrayIndexOutOfBoundsException). I'm upgrading to the newest CraftBukkit/Essentials to see if it's worked around.

Also, the combat system has always been terrible. It pretty much requires that you go in with overwhelming numbers of ships if you want enough left over to hold the star afterwards. Rather than 'I kill Wm number of your ships, then you kill Wy number of my ships until one of us runs out' it should really be risk style where you roll Wm dice and I roll Wy dice or something with an element of chance to it.

Just as a note, people pretty frequently leave signs saying "No entry" or something along those lines as a decorative element rather than a serious warning (for example, they were pretty common in the subways on past servers). You might want to elaborate when you leave signs that people should actually not enter or throw switches. If you're building something you genuinely don't want others to get into, though, maybe a multiplayer server isn't the place to do it.

Heh.. http://i.imgur.com/ZTo5S.jpg

Server's updated to 1.7.3 - it's okay to update clients now.

Should grab the last backup from http://www.idlemc.com/past-epochs/ and see what became of your pit. Hint: Nothing.

Fixed! The permissions got wiped at one point ages ago, so yours probably got lost them.

May I suggest fencing it off?

Backups are manual when I change something, usually. I last took one before upgrading to 1.7.2 this morning.

As far as I know.

We're updated to 1.7.2 now - this is supposed to fix the known piston endless loop issues.

Maybe, but I'm not 100% certain it was Squid's water valve that broke it. And since, once it happens, there's no way to go into the world and remove it, I dont' want to take any chances. The current rumor is that any piston that's self-activating (piston pushing its own activation lever) causes the issue. I've also seen reports of it happening if the piston pushes the redstone trigger that acitvated it (piston topped by a block topped by a pressure plate). Others have said that putting redstone directly on the piston causes an issue, and there are also reports that pistons in water can cause crashes (though that last one may have been fixed in 1.7.1). There just seem to be too many save-corrupting bugs right now for me to be comfortable with enabling them. And in any case, most of you are on the honor system to not use them. If you must, go ahead, but if you break the server, I'm calling you out on it here when peoples' work is lost

I've restored a backup from this morning so the server should be back up and running. For the moment I've added pistons to the banned items list. For those of you who have permission to bypass that list, please don't use them until we can be sure this is fixed. (Sorry about your ship, Laxan)

Yep... inecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) at net.minecraft.server.BlockPistonMoving.a(SourceFile:136) at net.minecraft.server.BlockPistonMoving.e(SourceFile:104) Happens whenever the server starts up now. Guessing someone found a bug with pistons. Since I can't log back in to fix it, we can either revert to the backup I took before the update this morning or wait for 1.7.2 to hopefully fix it.

Updated! Though my texture pack isn't, so pistons are now Ghost Pistons

Plus I forgot to capture a big chunk of the middle of the game for the DVD commentary. *sigh*

From the color schemes file: Dark Green - Rainforest Brown - Swampland Light Green - Seasonal Forest Light Gray - Forest Dark Gray - Savanna Yellow - Shrubland Cyan - Taiga Orange - Desert Magenta - Plains Blue - Ice Desert White - Tundra Pink - Hell

Nice looking output, but it requires X. Dynmap is actually pretty efficient, it's just that when there are a lot of people online, rendering on chunkload causes a lot of tiles to get re-rendered unnecessarily. The reason we originally moved away from a standalone mapping tool was that the memory cost of doing the whole map at once every night was exceeding the amount of memory in the machine and causing it to swap to disk, which made the game itself unplayable. Rendering individual tiles on-demand spreads the load out much more effectively.

Oh, I misread and thought he was saying 1.8 was coming in November, but you're right, he was talking about the 'final' release. Btw, I disabled rendering map tiles on chunkload, which should save some cpu/memory. It also means new chunks won't get mapped if you wander out into the wilderness unless you change a block in them. There's a new version out with a chunkgenerate event trigger that should be much more efficient, and I'll install that tonight. Plus, it supports biomes

Server was swapping big-time. I just restarted the server and it cleared up. This has been happening ever since 1.6.x - I think there're still memory leaks in there

Looking into it. Remember, for technical issues you'll probably get a quicker response by PMing me.

If 1.8 is really coming sometime after November, we might even reroll once again between now and then. In th epast we've only gone about two months per world. This last one only lasted so long because nobody noticed (or at least I didn't) that it had been so long. No point doing a new roll for just pistons, though

Yeesh, it was me. Just trying to be helpful, sorry. I meant to put your sign back, and I guess I forgot

The world is re-rolled! Log in and enjoy!

Alright... how does an hour from now sound? Let's do it! (Possibly meet on the server for the traditional dynamiting of the world, then re-roll once we're bored of that?)