Method for saving wireless energy storage based on multithreaded machine characteristics

Equivalent but non-essential description: For multithreaded machines, as long as there is one wireless energy hatch, all energy hatches are considered wireless.

That is, you only need to attach a very small wireless energy hatch to make the wired energy hatch/laser hatch that actually "supplies energy" also be treated as wireless, saving the large number of 4A wireless energy receivers needed to upgrade large energy hatches/laser hatches to wireless.

For Simple and Normal, you can use a huge IV wired laser hatch to "supply power", a 256A IV wireless energy hatch to trigger the wireless check, and two normal energy hatches to provide the voltage tier; or a 2A LV wireless energy hatch to trigger the wireless check and one normal energy hatch to provide the voltage tier.Simple and Normal are already very cheap because they can use IV lasers—do you really need to save on this too?For Expert, you can use two energy hatches of the same tier to step up the voltage, where one larger energy hatch/laser hatch is used to "supply power", and the other 2A wireless energy hatch is used to trigger the wireless check.

The actual principle is as follows: the intended effect of a multithreaded machine is equivalent to placing multiple identical machines, copying the configuration including the energy hatch size. If all threads still consume energy from a single set of energy hatches, power failure is inevitable. Therefore, when at least one energy hatch is a wireless energy hatch, the machine skips the physical energy hatch buffer, and each thread independently draws power directly from the wireless energy network. (If you have observed a wireless energy hatch while a multithreaded machine is running, you will find that its buffer never drains.) However, at this time the rated power is not changed to the sum of all wireless energy hatches; it is still the sum of all energy hatches, which is equivalent to treating the other energy hatches as wireless as well.It is said that in practice, at this time the machine also calculates the total energy consumption of the entire recipe at the start of the recipe, then subtracts this amount from the wireless energy network at the start, and no longer consumes energy during the process. I have not verified this conclusion.

In particular, Rampage No. 1 is not recommended to use this method to save materials, because the energy it uses to start fusion is still drawn from the actual buffer of the energy hatch, and only the energy for running the recipe is eligible for the above method. Using this method may cause startup to stall.

A curious reader may want to know what the effect is for multithreaded machines without a wireless energy hatch. The test result is that multithreading no longer occurs, and the maximum parallel count is multiplied by the thread count. A very mysterious feature is that, in this case, regardless of the actual parallel count/number of overclocks, the energy consumption is always equal to the sum of the rated power of all energy hatches.

This feature may be slightly unbalanced and may be fixed in the future.