You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A nice to have feature would be the ability to define several "material sets".
Currently any block type is allowed for the chip material, and whatever is configured for IO blocks is used. In order to build chips densely, you must use /rcactivate and specify the IO block types you want to use if they are different than the default.
A nice feature may be to have the ability to define material "sets", based on chip block type. So for example you could have the set:
STONE_BRICK,NETHER_BRICK,LAPIS_BLOCK,COBBLE
If a chip is activated using STONE_BRICK as the chip material, then use NETHER_BRICK for inputs, LAPIS for outputs, and COBBLE for interfaces.
If a block type that is not associated with a material set is used, then just use the default block types as is done today.
Your average user may never use this feature, but having it when you need it saves you the trouble of having to activate chips via the commands (I always mistype things so it takes longer than it should) and would allow you to build more complex circuits a little faster.
The text was updated successfully, but these errors were encountered:
A nice to have feature would be the ability to define several "material sets".
Currently any block type is allowed for the chip material, and whatever is configured for IO blocks is used. In order to build chips densely, you must use /rcactivate and specify the IO block types you want to use if they are different than the default.
A nice feature may be to have the ability to define material "sets", based on chip block type. So for example you could have the set:
STONE_BRICK,NETHER_BRICK,LAPIS_BLOCK,COBBLE
If a chip is activated using STONE_BRICK as the chip material, then use NETHER_BRICK for inputs, LAPIS for outputs, and COBBLE for interfaces.
If a block type that is not associated with a material set is used, then just use the default block types as is done today.
Your average user may never use this feature, but having it when you need it saves you the trouble of having to activate chips via the commands (I always mistype things so it takes longer than it should) and would allow you to build more complex circuits a little faster.
The text was updated successfully, but these errors were encountered: