How can I make 24 rotation states of block across blockstate?

[alexfadeev]

Hi!

 

First of all: I'm not a programmer at all. I just have a one task for myself and I need to resolve it.

And sorry for my English.

 

 

So. I try to add a block in world, which can set in all 24 states of rotation. I hope, you understand what I mean.

I try to do this cross the blockstate property. I think — it is most easy way. But I have 2 properties: Facing (UP, DOWN, NORTH, EAST, SOUTH, WEST) and BINDING (LEFT_TOP, LEFT_BOTTOM, RIGHT_TOP, RIGHT_BOTTOM). That in turn gives you 24 different state.

 

I know that blockstate it is just 4 bit and it have 16 state variations.

 

So, my question. How can I resolve this problem? Maybe somebody have ready-made solution or some topics, where I can read about multiple state of blocks? How can I make 24 states for my block?

 

Thanks for you help.

[diesieben07]

First of all, I would really really like some insight of you on this rotational stuff, because I have been beating my head against this for like a week and it's a) beginning to hurt and b) I still haven't figured it out.

 

For the rest, you can make block states based on properties in a TileEntity. You use getActualState in your Block class to transfer the data from TE into the IBlockState.

[jeffryfisher]

If I understand your 24 states:

 

1) I can choose one of six faces to face me

 

2) I can then reach out, grip that face and dial it to choose one of its four adjacent faces to face UP. If I were holding a face with an arrow printed on it, I could point the arrow UP, RIGHT, DOWN or LEFT.

 

If your game purpose really needs to retain all of that information, then you do indeed have more states than can be kept in metadata. You'll need a TE as d7 suggested. If game effect really only hinges on one face (or allows you to calculate some of your data from neighbors like walls and fences do), then you can avoid the TE. If calculable, getActualState is where you'd do so.

 

What are you trying to do?

[jabelar]

One other solution is to actually have two different blocks with the various states distributed between them. When someone performs certain rotations then you'd replace with the other block (with corresponding rotation state). If both blocks extend the same base block, then you can test for the base block anywhere your code needs the block.

 

But tile entity is better way to go. Just wanted to say that there are usually multiple options to solve problems in programming.

[alexfadeev]

I making a room:

 

 

How can you see, here is 10 different blocks. They should be have 24 position states, because:

 

This is only one wall of room. But room have 6 walls. =) And yes, this is room from "The cube: Hypercube" movie.

 

I do not want make a many same blocks in different position. So I cut them to a minimum the number of unique blocks. And now I need to rotate them for construct my room.

 

 

I think, I will use TileEntities for resolve this. Now I learn about this.

[Choonster]

First of all, I would really really like some insight of you on this rotational stuff, because I have been beating my head against this for like a week and it's a) beginning to hurt and b) I still haven't figured it out.

 

For the rest, you can make block states based on properties in a TileEntity. You use getActualState in your Block class to transfer the data from TE into the IBlockState.

 

I'm obviously not the OP, but I managed to make a relatively simple block that stores its facing (just the standard

EnumFacing

values) in its

TileEntity

. You can see the implementation here:

[url=https://github.com/Choonster/TestMod3/blob/da28151e33cd2f3bb9f7db1478e862fab629f220/src/main/java/com/choonster/testmod3/block/BlockColoredRotatable.java]Block[/url]

,

[url=https://github.com/Choonster/TestMod3/blob/da28151e33cd2f3bb9f7db1478e862fab629f220/src/main/java/com/choonster/testmod3/tileentity/TileEntityColoredRotatable.java]TileEntity[/url]

, blockstates file

 

Getting the facing synced correctly between all players was a bit tricky, but I just needed to call

World#markBlockForUpdate

when rotating the block to send the

TileEntity

update packet and when receiving the packet to update the model with the new facing.

[diesieben07]

Yes, one facing. That's easy. But the Block can also be rotated around that facing, to achieve all 24 possible states.

[Draco18s]

Yes, one facing. That's easy. But the Block can also be rotated around that facing, to achieve all 24 possible states.

 

Hold on. If you have 6 states and TWO rotations, that's almost 100 total states.

[diesieben07]

Hold on. If you have 6 states and TWO rotations, that's almost 100 total states.

Wut? No no.

You have 6 possible "front" faces. And 4 possible rotations for each.

[Draco18s]

I misread something. Probably as a result of having zoomed in on my tablet screen.

[Choonster]

Yes, one facing. That's easy. But the Block can also be rotated around that facing, to achieve all 24 possible states.

 

I managed to extend my previous example with a face rotation property:

[url=https://github.com/Choonster/TestMod3/blob/dee37427c6851507b30409e995dce21ee150c33c/src/main/java/com/choonster/testmod3/block/BlockColoredMultiRotatable.java]Block[/url]

,

[url=https://github.com/Choonster/TestMod3/blob/dee37427c6851507b30409e995dce21ee150c33c/src/main/java/com/choonster/testmod3/tileentity/TileEntityColoredMultiRotatable.java]TileEntity[/url]

, blockstates file

 

Having a block with so many possible combinations of properties makes me glad that Forge's blockstates format exists.

 

This should be pretty similar to what you're looking for, alexfadeev.

[jeffryfisher]

Even after figuring the data storage, you'll need to solve the placement problem. How will you control the secondary rotation? Perhaps right-clicks on an already-placed block can rotate it around its facing axis. It might actually be less work to make four different blocks.

[alexfadeev]

Even after figuring the data storage, you'll need to solve the placement problem. How will you control the secondary rotation? Perhaps right-clicks on an already-placed block can rotate it around its facing axis. It might actually be less work to make four different blocks.

 

I want resolve this cross the rotationYaw and rotationPitch. Thats why I called them LEFT_TP, LEFT_BOTTOM etc.

Actually all 24 states can be placed only with this properties, without EnumFacing. But with facing it will more reliably.