Thanks, no problem. It is procedurally generating each chunk, on the fly, not loading anything at the moment. Once I implement caching to disk, it only needs to generate a given chunk once, and then it will load pretty much instantaneously (as it stands, each chunk is exactly 1 megabyte worth of data). One reason it goes a bit slow is because it is so unoptimized - it is processing every voxel, even the where the air is (to some extent), and where the ground is completely solid and invisible - hence there are tons of wasted computations on empty/completely filled areas. I am going to speed this up a lot in the future. Like I said, its very unoptimized, should load much faster eventually :)

I am aiming to get it "playable" as soon as possible. One of the first things I will implement is some basic destruction and construction (probably), after I optimize everything a bit. It will probably function a bit differently than Minecraft since everything is a little less cuboid - i.e. you will have to level out terrain or build a foundation for a level building, obviously. But otherwise, there will be some similar ideas: resource collection, RPG progression for all items (tools, weapons, clothing/armor, etc).

Hi Chris - I am actually working on a new system for generating terrain (not just various noise algorithms, but a rough simulation of tectonic plate movement, kinetic and chemical erosion, watershed, lava, etc). Same engine (of course), just adding in some new algorithms. I do not want to spend too much time on terrain, but I am going to see if I can crank out anything quickly - if not I will just resort to simpler methods.