It is also possible to use 'Set requests' at the same time as 'Read contents'

Yay?

…, due to a little bit of magic self-subtraction of the circuit network signals.

Oh. Did the attempt to add a wire selection for most/all circuit control options not work out, or are you hiding that for a later FFF?

However, the asteroid processing recipe duplicates itself, so sometimes during normal production, no item count decreases either.

You could arrange for an inserter that prioritizes removing the output asteroids. As long as the inserter either removes an asteroid or becomes/stays idle before the ...

The wires make no distinction where the signal came from. They simply sum up the outputs of all connected entities and then provide that as the input to all connected entities in the next tick. Thus the train station sees its own signals once per connected wire. With no connected wires the control ...

You're requesting more bots than can fit the roboport. All requests above what can fit are ignored; see 132980.

How do your schedules and interrupts look like? From what I can tell, as long as the train hasn't moved and is still picking its destination (zzz icon), the stations signals are still available. There are two things you'd have to watch out for to keep the train in that state if no valid destination ...

I am not sure if there are good solutions that would not be making this logic more fragile. Having lab throttle down as the technology approaches its max would require converting remaining progress into science packs which needs to account for productivity and if this logic throttles too much it ...

Expected behavior: either quality is rolled when crafting begins and that result is locked in, or quality is rolled based on the machine's state at the moment the result is produced.

Both of these are exploitable by controlling speed beacons with power switches. Currently quality is rolled at ...

it is tricky to understand when a train would pass through a waypoint without stopping even if it has a condition, like "cargo empty"


It's very simple: A stop is a waypoint if, and only if, its schedule entry has no wait conditions; the train will not stop, except for "no path" situations. If ...

You could configure the assembler to read the ingredients and use that as input for your decider. Might require you to use the other wire to prevent signal contamination and is mutually exclusive with reading the contents. And it obviously won't work with recipes taking no ingredients.

If Alien Biome was downloaded 681k times and there were say 50 updates to it and people who played it regularily downloaded on average 20 of those updates, then Alien Biome counts only for 681k/20 = 34k users.

The mod portal explicitly says: "Downloaded by: 681K users", which I believe are ...

At level 2 modules having 4 quality nets you 6.4% "net" quality = 6.4 quality items per unit of time that the assembler makes 100 units of output.
Compare this to 4 quality and 1 speed (still level2) and your output is 7.15% "net" quality = 7.15 quality items per 100 units!

You might want to ...

We have dynamically sized configurations elsewhere: Blueprint books and sections in constant combinators and logistics requests and add another row whenever their final slot gets filled. Can't that system be used here as well to remove the arbitrary limit altogether?

You are placing the signals while the rails are already there? I'd need a proper screenshot or save to confirm, but if sounds like you're initially placing the signals rotated the wrong way. How are you placing them? Do you have a proper signal or signal ghost in hand or is it a blueprint of a ...

isn't it problematic that it cannot detect wether the (full) belt is moving or not ?

Depends on the use case. While the OP may have wanted that, it wasn't stated in the goals nor did I need it.
For moving/stalled belt detection I already have a separate bp: Two splitters, one belt apart, and ...

different approach to make the list more manageable: 132531

I happened to need a timer based on signals not changing for my own save; only the single signal version though. A vectorized version of it turned out to be much less annoying than I initially expected (only one extra combinator). From there, all that's left to fulfill the goals as stated in the OP ...

Way too many combinators. One constant, one decider and one arithmetic are sufficient. The arithmetic is only for signal isolation/merging and might be able to be removed in 2.1. The conditions in the decider might be a bit more complicated than necessary, but I recall having the recipe switch ...

Your repetition counts are far too low to have statistical relevance.

The both setups are essentially a self recycling loop, only the input you count is one step before that loop. A standard self recycling loop takes 2726.9095067473136 common per legendary; accounting for the +200% prod in your ...

Shift everything except for the rails one tile to the left and everything will line up properly.

As the others have already mentioned, rails align on a 2x2 grid. So, if you are designing a blueprint that includes rails, start with the rails (or at least put a rail on top of the planned rotation ...

The only thing left is the inconsistent behavior between the map editor (I can't place thrusters) and remote view (I can).

From what I recall from the attempt of eradicating fluid mixing during 1.x (or was it still 0.18 at that point?), this is intentional. There always was some corner case ...