Guides#85English
The clever idea of the biological extractor maintaining no-consumption recipe products and automatic synthesis

The clever idea of the biological extractor maintaining no-consumption recipe products and automatic synthesis

The mechanism of the biological extractor is quite special, making it troublesome during automatic synthesis. This article addresses two functions: fully automatic initialization and maintenance of full-brake no-consumption formula products. (To be honest, I'm just too lazy to do more.)

All consumables mentioned below have automatic synthesis channels by default.

First is fully automatic initialization. Write the order of consumption: Concentrated Cloud Essence, Fire Water, Light Air into the order template in sequence. Mark the order arbitrarily, and place it into a pattern provider adjacent to a quad input hatch. This quad input hatch maintains the input of nutrient essence; block two slots, leaving one. The output bus crafting card automatically requests the order, and the remaining slot will automatically fill with the first liquid in the template recipe, thus achieving initialization by consuming the corresponding liquids in order after the machine is enabled.

However, one thing is that this method will continuously occupy a synthesis memory in the network. If you mind, you can put the sample provider into a subnetwork.

See details in the image below

The clever idea of the biological extractor maintaining no-consumption recipe products and automatic synthesis
The clever idea of the biological extractor maintaining no-consumption recipe products and automatic synthesis

For recipes that consume materials, the programming bay can be used. The template writes virtual items and consumed materials. The template supplier enables the option to block insertion of non-identical templates (or template assembly). After the request is made, the machine automatically initializes and then completes the recipe.

For recipes that do not consume materials (such as villager eggs producing brains), if you don't want it to keep producing, you can also automatically maintain a certain quantity.

First, each recipe of this type requires a programmable compartment to prevent potential issues. Connect two precise output buses to the programmable compartment (I'm not sure if the throughput of a modified normal output bus would be too large and cause problems, so I choose precise output buses). A hypercube can be used. The following uses villager egg production of brains as an example. One output bus is used to output the virtual item corresponding to the unconsumed ingredient (virtual villager egg), and the other is used to output a virtual item of any unused item (such as any virtual circuit) to overwrite the virtual villager egg. Both are placed with redstone cards and both are connected to standard transmitters. The standard transmitters are all marked with the product (brain).

The precise output bus corresponding to the virtual raw material (brain) is set to no signal activation, the transmitter is set to quantity greater than the emitted signal, this number is the lower limit for maintaining the product, below which it will overwrite the virtual raw material to the programming warehouse.

Another precise output bus is set to have signal activation, the transmitter is set to a quantity greater than the output signal, this number is the upper limit for product maintenance, and if higher, it will overwrite useless virtual items to the programming bay.

Avoid setting the lower limit higher than the upper limit (should be only those who miscount zeros, right?)

It is recommended to increase the numbers under the premise of not lacking essence, and increase the gap between the two numbers to prevent repeated jumping and consumption of additional resources.

The clever idea of the biological extractor maintaining no-consumption recipe products and automatic synthesis

When the storage quantity is less than the lower limit (and necessarily less than the upper limit), all transmitters are turned off, continuously covering virtual materials, producing items.

When increasing beyond the lower limit but below the upper limit, the virtual material stops continuous coverage, and the recipe is still running until it exceeds the upper limit.

Exceeded limit, virtual unrelated item transmitter signal off, continuously covering unrelated items, production halted.

After being consumed, when between the upper and lower limits, it remains in standby, and unrelated items stop covering.

Re-cover virtual material when below the lower limit

Thus achieving passive maintenance of the corresponding item.

Virtual items will continuously output coverage in certain intervals. Although it enhances stability and has no adverse consequences, it feels weird.

Setting the output bus to pulse mode may lead to unexpected situations and greater harm, so it was not chosen.

Contributors

Comments

0