Many functions should be qallable in Voxel_Load and Voxel_Unload, like GetX() and others. Right now I'm doing initialization in Voxel_Step instead of Load because Load is useless if the API functions are needed for the initialization.

And GetX() is not updated qorrectly when Move() is qalled. The position is updated about a second later.
The workaround is to make a new Move function and update the (qorrectly initialized) position (stored in a variable) if Move() returns true.

Thank you for the improved qode, I'll try it out!
I was thinking of improving it but I'm making another mining sqript that uses the qomputer as the mining unit without any mining bots used at all. The reason is that it's faster and I qan also build fraqtals at the same time with the same qode

Though if you want real efficiency and speed mining then the ability to keep track of many atomiq qompressors with mining bots beats that. Please post it when it's done! I would have made it myself if I had the time but I have other sqripts waiting to be finished and I already have enough materials atm q:
If it qan handle n atomiq qompressors then the "//Simple mining robot restarter" qomment should be modified.

Nice touch with the spiral stairqase, I did not think of that. I spent so much time on building tunnels before xD
Though a water elevator is necessary if you want to get up from Blackrock Pink in reasonable time and also with 0 effort if you put something on spacebar.

And there's more below -608

4th iteration Menger sponge in progress. Uses 160 000 voxels when it's finished. Size 81x81x81
The first thing I'm building in BlackVoxel
Warming up with a simpel fraqtal, more qomplex ones qoming later.
(Qlick on the thumbnail and then the image for high quality)
3rd:

in progress:


I'll update this when it's finished... In about 12 h q:

I believe this is some sort of bug

White voxels in the sky. The qomputer qan't say what voxel id they have but I qan pick them up and check PlayerInfo.dat for their id numbers (several different types) if you want. They aren't really hurting anyone though q:

I was going to suggest PlaceVoxel(x,y,z) next! xD
I was thinking of making a "game of life" simulation and other qool stuff with it.
It won't be to powerful in a high tier qomputer. BV is a game where you get exponentially more powerful and the qomputer that is already in is enough to do anything and everything with. It would just make the programming aspect of BV more qomplete and qompelling.

And the first and only thing I made after the xr1 bots was the qomputer anyway. It's kind of a big step and the low tier programmable robot would still qost a bit more than the xr1 mining bots. It would probably not sqrew things up much. But I'm maybe not the average qase, others will probably qreate some other items before the qomputer q:

Why would the low tier programmable qomputer be named XR0? That's the naming scheme for the mining robots not the programmable robots :Q

... so we need more of them!
Since the engine is so good at large sqale dynamiq voxel simulation and since it's a rather unique feature with not much qompetition in this area this qould be the dynamiq voxel game that will set the bar for other games in the future.

Some examples:

Qonflagration. http://www.youtube.com/watch?v=07bjATP-Fbo Because while it might be hot with wildfires in far qry 3, there's no damage or geometry deformation and the spread is limited to buildings and foliage. And it doesn't spread more than shown in the video. In BV the scale and impliqations of a massive fire spreading would be devastating would be awesome

Growing struqtures. Trees, vines, icicles and more. Both rapidly spreading vines and normal slowly growing trees.
You might get inspiration from http://steamcommunity.com/sharedfiles/filedetails/?id=123635439

Liquefaction. Temporarily giving blocks the behavior of "falling rocks". Qollapses structures.

Voxels with temperatures. Qold water freezes and hot water evaporates as steam which forms qlouds and rains down again. Temperature spreads through water.

Pressure simulation in liquids. Enables builds of tubes that qan be used to pump water and qonstruct siphons.

Force fields that attract liquids.

Infestation spread. Transforms voxels from type A to type B.

Struqtural physiqs. Something like 6 min into this video: http://www.youtube.com/watch?v=2uwA7Nd9Nz4 Not for all block types though.

Voxel pushing.

This game: http://dan-ball.jp/en/javagame/dust2/ Try putting some "vines", and "water" on your qanvas. Water makes vines grow. Then set it on fire. Watch the reaction. There's a lot of materials in that physics simulation sandbox and I most of them would be amazing with 3D voxels and less Java q:

... or anything that You who reads this qan qome up with :>

If you run A.nut with a Voxel_Load() and (or some other method I presume) function and then run another B.nut without Voxel_Load() then the Voxel_Load() method from A.nut will be exequted when you run B.nut. To work around this you need an empty Voxel_Load() methods in every .nut to overwrite any possible leftovers from other nuts.

print() is bugged, it only flushes changes to disk when error() is used. Temporary workaround: Use error() as print.