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
There are a couple of blocks that would make sense to provide a comparator (or comparator-like, using something like the RS Detector) output based on network conditions.
The 2 immediate suggestions are:
Controller - support comparator output indicating either:
amount of power stored (0-15 scaled current storage value
current rate of power consumption (0-15 scaled usage/tick, maybe averaged over some period?)
(Alternative) 'Alarm' signal - comparator reports only 0 or 15, and toggles when stored power drops below some lower threshold (either fixed or GUI-settable). Resets (to 0) when power rises above upper threshold (to simplify 'anti-strobing' protection devices when network isn't getting enough power and flickers on/off rapidly. Also possibly reduces number of comparator updates compared to other output options)
Disk drives/storage blocks - comparator reports fill ratio of the contents of the disks (not the number of disks present in the drive). So a drive with 1x 4k disk, 50% filled with stuff, reports redstone level=7
Ideally there would be some way to query (disk) space available on the whole network, but I'm not sure what block would be appropriate to report that, or if it's even possible given things like external storages, etc.
Other ideas:
Network transmitter - reports current power consumption (which is either static or 0 as I understand it, although might be useful now that cards can be add/removed from Tx) - so power-hogs can be disabled without taking down the network.
Solderers - reports number of items being processed (0 = empty or incomplete, 1-15 scaled to number of valid recipe batches (so 64x basic printed, 64x redstone, 64x silicon printed => 15, 32x prev = 7, but 64x basic printed, 64x redstone => 0 (invalid recipe))
interfaces - amount of items in 'supplier' slots (this might actually work already?)
fluid interfaces - qty of fluid in the output tank
What happens:
These features do not exist.
What you expected hope to happen:
That the lovely people who do the work consider doing this extra work :-)
Version (Make sure you are on the latest version before reporting):
Minecraft: 1.10.2
Forge: 2215
Refined Storage: 1.2.18
The text was updated successfully, but these errors were encountered:
Issue description:
There are a couple of blocks that would make sense to provide a comparator (or comparator-like, using something like the RS Detector) output based on network conditions.
The 2 immediate suggestions are:
Controller - support comparator output indicating either:
Disk drives/storage blocks - comparator reports fill ratio of the contents of the disks (not the number of disks present in the drive). So a drive with 1x 4k disk, 50% filled with stuff, reports redstone level=7
Ideally there would be some way to query (disk) space available on the whole network, but I'm not sure what block would be appropriate to report that, or if it's even possible given things like external storages, etc.
Other ideas:
Network transmitter - reports current power consumption (which is either static or 0 as I understand it, although might be useful now that cards can be add/removed from Tx) - so power-hogs can be disabled without taking down the network.
Solderers - reports number of items being processed (0 = empty or incomplete, 1-15 scaled to number of valid recipe batches (so 64x basic printed, 64x redstone, 64x silicon printed => 15, 32x prev = 7, but 64x basic printed, 64x redstone => 0 (invalid recipe))
interfaces - amount of items in 'supplier' slots (this might actually work already?)
fluid interfaces - qty of fluid in the output tank
What happens:
These features do not exist.
What you
expectedhope to happen:That the lovely people who do the work consider doing this extra work :-)
Version (Make sure you are on the latest version before reporting):
The text was updated successfully, but these errors were encountered: