unfortunately, the world isn\'t as simple as it seems on the surface.
in order to implement the last set of sideways orientations, the block (the actual physical block placed on the ship) would need to have just 1 more bit of data. if you consider the possible permutations of orientation on a corner vs other simpler block types, this might make sense, the more possible \"positions\", the more data is needed to track each given orientation.
Sadly, schema has already maxed out the usage of each bit per block without adding an entire extra byte, given that each block already is using 3 bytes, you can imagine the slowdown this could cause. He even stole an extra bit from the \"activation\" function, which is where the \"if you push R when facing a corner, it changes\" bug comes from.
Schema IS working on this, and plans to add more block shapes later on (core fire, expand content later right?)
All i can ask is this, you see how active schema is, he DOES fix simple stuff fairly quickly, so if it doesn\'t get fixed for a good deal of time..., you should probably figure that its more complex than you are estimating, i often find that to be the case.
(about the universal wedge, or any block, orientation based on player view or placement or any other number of setups, i love this idea, as an option. But its an interface/GUI improvement, and so sadly will likely have to wait until higher priority things are complete before it can be looked at.)
