How to ensure running recipes (dyeing + blocking output) when dense parallel multi-blocks lack independent chamber positions

A while ago I made a platinum processing setup, as seen in the header image, the machine is very compact. Some people asked about the machine architecture, in reality it's just stacked together, one machine per recipe. The difficulty lies in: with such a compact connection, the intermediate machines each only have one non-shared inventory slot, so how can we ensure that recipes don't get mixed up?

My friend and I also thought about it for a long time, and several times we wanted to split it into several groups of 2x2x2 machines, but in the end, we came up with this method of spray paint can dyeing + blocking the output.

Spray Can, can be used to dye input/output hatches, hatches of the same color will be bound together.

For example, if a machine has a pair of yellow input/output and a pair of green input/output, then the products obtained from the yellow input will be in the yellow output, and the green will be the same. At the same time, a recipe split between non-matching colored inputs will not be recognized.

Several relatively important situations (affecting understanding of the following text):

1. If a machine has an A-colored input but no A-colored output, it will output from any output slot, even if it's not the same color.

2. If a machine has an A-colored input and an A-colored output, but the A-colored output is blocked, the machine will not allocate other outputs to the A-colored output. Placing reactants will prompt that the output is blocked and no reaction will occur.

In this case, each intermediate machine only has 1 non-shared chamber slot, and not many shared slots either, but each requires dual fluid and item input/output for a total of 4 chambers. Theoretically, the output chambers could be shared by 4 machines with two fluid outputs and two item outputs, but this would make it impossible to control unique recipes by blocking outputs later on, and would only allow machines of the same color to share output buses and chambers.

Maintenance hatch on top and bottom, wireless energy hatch shared by 8 machines, coil shared by 2 machines.

First, assign a color to each row. Here, we divide into 4 groups: Group A is red, Group B is yellow, Group C is blue, and Group D is light blue:

Input buses and chests must be unique to each machine and cannot be shared.

And as shown in the figure, the input hatch is located in an independent hatch slot, and the input bus is located in a shared hatch slot of a non-colored machine.

Buses here will cause reactions, the solution is later.

Output buses and chests of the same color can be shared, because according to our design, machines of the same color in a row will not have shared inputs. Conflicts in input chests are entirely resolved by machines of different colors.

If you've been following along carefully, you'll notice that using Machine A1 as an example, we currently have:

1. Red Input Bus/Chest

2. Red Output Bus/Chest

3. Blue Input Bus

4. Yellow Output Chest

Each other machine is the same, with an extra colored input bus and an extra colored output hatch.

The output color does not affect this machine, but the input does.Mentioned in the special case 1 of the spray can.This will cause, for example, machine A1 to read the item input of machine C1, and if there is an item-only recipe, it will cross machines.

It is very simple to resolve this conflict, just use the special case 2 of the spray can mentioned earlier.

For example, with Machine A1, if you don't want the blue input bus to interfere, you can add a blocked blue output (for example, block it with something completely unrelated like paper and steam), as shown in the figure:

tips: You can use the cut and paste helper to conveniently place clogged chambers

Colorful, but very compact~

tips: Uses photos from the Camera mod for reaction annotations