What is BLOCK_SIDE, and why does it consume 8 bits?

You could half the number of bits needed by using a 3 bit number for the block side. So for doors (assuming that one bit is whether to door is open) you still have 3 bits free.

I could allocate some more, but I thought (e)ndless redstone would work better and is less annoying.
It wouldn't make it slower at all, but a second array redstone_state[SIZE][SIZE][SIZE] would make more sense and is also easier for backwards-compatibility.
But I need neither of them, the most parts are already implemented

Edit: BLOCK_SIDE is 3 bits wide, but some blocks need some more bits and I'd like to have it as flexible as possible.

Both! Both tested, but 3.6 not regularily. The only ndless functions I use are hwtype(), isKeyPressed and fopen/fread/fwrite/fclose.

Edit: I just reseted the votes, removed lighting (doesn't work together with face-combining) and added minecarts (why not?)

No, face-combining is always active, but I could make it optional (as well as lighting), but it's not really worth the hassle.
I mean, just for aesthethical purposes calculating multiple textures, giving each vertex a texture ptr, light computation etc. would be way to slow.
The startup time would approximately triple, if not more and the chunk geometry calculations would get slower as well, but they would cause a noticable slowdown in game, as each block change (door opened, block destroyed, redstone changed, water flows etc.) triggers a recalc of the chunk and possible the adjacent ones as well..

Both! Both tested, but 3.6 not regularily. The only ndless functions I use are hwtype(), isKeyPressed and fopen/fread/fwrite/fclose.

Edit: I just reseted the votes, removed lighting (doesn't work together with face-combining) and added minecarts (why not?)

ok cool to hear, because I didn't feel like upgrading to OS 3.6 yet.

Yeah he said mobs would be easy but they'll come later I guess.

Quote from: Vogtinator on June 06, 2014, 02:10:58 am

I could allocate some more, but I thought (e)ndless redstone would work better and is less annoying.

With normal redstone, though, we can port "real" redstone devices easier.

Just the comparator, nothing more. And I don't think you'd build really complex machinery on crafti..
Anyway, I'll post a "redstone manual" to show how it will work. If you're familiar with minecraft's redstone, this shouldn't be a problem,
the differences are small and most minecraft redstone stuff will work directly.

V.

Are u planning on adding mobs into the game at any point because that will make the game a bit more interesting

but good job
 

I am, just vote for mobs in the poll at the top. But currently it seems you're lucky

Vogtinator, you probably forgot my question:

Quote from: mdr1 on June 03, 2014, 03:49:22 pm

Why do you need bits for opened or closed doors? Can't you just make a block which is an opened door and an other one which is a closed one ?

I answered it, directly below. It wouldn't make any sense NOT to use the BLOCK_DATA bits as that's basically their purpose.
And it wouldn't solve the compatibility issues either.