That took longer than expected - I wasted about 20 minutes going about it completely the wrong way, which I then realized, so I deleted all the added code and got it done :) Atm it only allows for one undo at a time to prevent heap space issues

I should probably point out that the bottom layer is bedrock, and unless you mine it for 2,147,483,647 act cycles, you're not going to be able to do it I'm in the middle of loads of exams right now, but once they're over I'll get back to this and implement inventories/crafting/more blocks etc. Oh and if you suggest something I'll implement it! Once I've improved the performance a bit, there's quite a lot I'd like to do with this :)

Just realized that this, which is the first scenario I ever made (not just first uploaded, first ever) has got the #3 most plays of all my (uploaded) scenarios >.< Might have to upload a couple later to try and counter that...

Also: public void act() { if(condition) { getWorld().removeObject(this); return; } //Any code here won't raise errors if the actor is removed, because the code exits out of the method through the return statement. }