However, it is only necessary because of the way Create obtains and retains the voxel shape prior to placement. That shape may not be valid, and may cause confusing placement restrictions. The problem is with circuits that don't have a base (a feature that didn't exist prior to v1.11). It would be easy enough to reimplement this for panels that do have a base.
Before v1.11, it was just calculating the base panel shape before placement: component voxels were calculated afterwards.
Forge microblocks curse free#
Calculate PanelBlock's voxel shape without a block entity object, probably with a static, context free method something like: calculateShape(CompountNBT cellData, Direction facing, Boolean hasBase).Determine player hit vector without the block entity and determine placement location within the block space.If a non-player is placing the panel (such as the when the Create contraption stops and becomes blocks again), again, we have to calculate the voxel shape before the block entity exists.Again, difficult without the block entity, especially since the existing voxel shape calculations exist within the PanelTile class. If the player is placing a circuit without a panel, it needs to calculate the voxel shape of the circuit prior to placement.If the player is placing a panel or a circuit with a panel, it would be easy enough to just use the voxel shape of the base.This is difficult without a block entity. If the player is placing a component in the world, it needs to calculate the location based on the player's hit vector.The ideal solution would be to calculate the voxel shape prior to placement somehow, but there are a number of obstacles, and a few different conditions to account for. Intuitively, most players would move around a little to try to place from a slightly different angle which would work, but it's not ideal. The problem is that the player could be standing at that spot and will have no idea why they can't place the first component. However, I'm not entirely satisfied with this solution and am still considering other alternatives. It's the most unlikely place that a player would be standing while placing. My solution was to make the pre-placement shape the tiny cube in the center of the block. The shape was empty to prevent culling of adjacent block rendering and to allow the player to stand within the block space when placing the first component. Create contraptions query for the voxel shape once before it gets placed. It needs the PanelTile entity to calculate where the tiny component will place. It doesn't know what shape it will be until after a component is placed. The issue is that the PanelBlock voxel shape is dynamic. Well, at least doors and levers can be interacted with while moving, and lever toggle takes effect when contraption reverts to blocks, so it might be possible to keep a circuit working "in isolation" too, maybe even keep tiny wireless transmitters transmitting. I also use "circuits" for decorative microblocks, would be nice to have them move visually and collide even if they aren't operational otherwise.īonus points if circuits remain operational and interactable while moving, but since even normal redstone doesn't work on moving contraptions.
Making them behave as if they were broken and placed in a new position, keeping only visuals while in transit, would be ok IMO. have the control panel inside elevator, instead of on the shaft wall on every floor.) I suspect that making circuits movabe with pistons would suffice for Create too.
If it isn't too much work, would be nice to be able to move circuits with contraptions. torches), and circuits disappear if a contraption reverts to blocks at their location (instead of dropping like e.g. They stay in place, contraptions pass right through them (like they pass through stationary e.g. However, it seems that the the circuits (with or without a panel) are not movable with Create. (At least a button for each floor, sending wirelessly to the control room.) Built an elevator using Create and was going to use Tiny Redstone for the control panel.
0 kommentar(er)
