#Linking Source Jars

7 messages · Page 1 of 1 (latest)

tidal shadow
#

Very simple thing to maybe save on the amount of particles generated from source relays (potentially multiple). Basically, just being able to use a wand of dominion on two adjacent jars so that one jar sends its source to the jar adjacent/above/below while the target jar isn't full.

Implementation:

  • Jars must be directly adjacent or above/below to be linked
  • A jar can only be linked to send to a single other jar and receive from a single other jar.
  • Transfer of source stops when the target jar is full.

In practice, you could have a stack of jars and have each one set to send it's source to the one below it while it's not full. Relay would only need to send to the jar at the top of the stack.

hidden axle
#

Just use collector and depositor relays

tidal shadow
# hidden axle Just use collector and depositor relays

Do these not generate particle streams like the other relays? I admit I haven't tried them yet. If they don't cause a constant stream of particles going everywhere, then yeah, that would work. Though, there are instances in which you'd want to control what is depositing/retrieving source from a given jar 'set' which being able to link jars would also allow.

hidden axle
#

Mostly it's that you don't need to link any jars directly. So you just route your incoming source to the depositor and it'll fill all the jars around it. You can freely add and remove jars as needed

tidal shadow
hidden axle
#

For control of where it goes, you can turn off relays with redstone. I usually have the collector send to a splitter, and from that splitter to the rest of my base subsystems

#

So I'd turn off the connections after that splitter