-
Notifications
You must be signed in to change notification settings - Fork 2
Encoder Guidelines
InfraRedstone has a strong focus on eliminating much of the confusion native vanilla redstone. As such, Encoder-scannable objects should be designed in standard ways based on their purpose.
Any object dedicated to item, fluid, or energy storage should output a value from 0-63 based on how full that storage is. If an object has more than one type of storage, the object may let the player choose which signal it will output for. Do not use the encoder for power monitor-style player-set value outputs. This is much better served by a standard infraredstone signal.
Some machines or other objects output different comparator signals based on their state, like the Botania runic altar or the cauldron. If there are six or fewer states the machine can output for, use a separate bit for each value. Otherwise, output the numerical value of the state.
Some objects, like the jukebox, hold a single item from a set at a time. If there are six or fewer items the object can hold, use a separate bit for each item. Otherwise, output the numerical value of the object.
If your object doesn't fit in one of these categories, file an issue and a project dev will help you figure it out. For the sake of server efficiency, Encoders do not currently scan entities. If you want entity interaction, please add a tile to perform the interaction between the encoder and the entity.