Bots prioritise yellow chests over red, so on Gleba I put produced bioflux to a red chest, offloading most spoiled to a yellow chest for local use.

I set up an inserter which offloads most spoiled eggs to a heating tower if there are more than N in a chest.
Works well your production is running constantly, as I beleive it should on Gleba

These two outputs overlap. Please allow specifying wire color for each.

The case: I'm trying to upload to an assembler an exact amount of ingredients needed for one item to be crafted, and currently I need to keep a list of ingredients in a constant combinator.

1) Set small requests for an item less than a stack size not far from each other, for example, yellow belt, min=5, max=20
2) move any slider just a little bit
3) both requests are being reset to 0

My particular usecase is that modifying max to infinity also resets min to 0, which is extremely ...

Thruster consumption number for Rare quality looks weird. Should it be just 9.6?

If you control requests with circuit network, you can request one stack of items using selector combinator.
It has an option "Stack size" which outputs a stack of items for every signal it receives.

If you have a request larger than one stack you can also round it up to a number of full stacks with ...

Maybe this could be solved by allowing inserters to use "*" (everything or anything) signal as a filter.

For logistic network I kinda solved it by offloading fresh products to a storage chest (yellow) with an inserter, and then unloading most spoiled to a passive provider chest (red) when yellow has more than N items. From the red chest most spoiled get offloaded right into a heating tower in the same ...

danbopes wrote: Thu Nov 21, 2024 10:11 pm Buckets will just reduce functionality for no good reason.

I think that spoiled value should be kept, and buckets added just to simplify products management, and maybe UI, eg specifying a filter for a belt splitter.

+1 to this.
Also I feel like there should be not a value but a few buckets similar to quality, eg fresh (100%..75%), mildly fresh (75%..50%), not so fresh(50%..25%) and nearly spoiled (25%..0%). It should also allow insertes to pick more spoiled or more fresh from each bucket.

My usecase: I want to ...

aka13 wrote: Wed Oct 23, 2024 7:19 pm it literally tells you that shit will break with a huge button

Actually, it only says how awesome the new version is (and it is!) and nothing about remaining saves.
Also, this screen shows up after an update, when I can't do anything to prevent that.

After a recent update I have to make huge changes to my 1.1 base to keep playing, e.g. rebuild all curved rails with new ones (still cant believe this).

I suggest that there is a warning for 1.1 players which tells about irreversible incompatible changes they will face after an update: 1) that they ...

no rebuilding work should be "required"


I try to expand my rail network to fix fluid warnings, and I end up with this kind of rail placement (see attachment). I can not see how I fix that in a good way without rebuilding the whole intersection, which would require rebuilding all rails around it ...

After an auto-upgrade to 2.0.8 from the latest 1.x release some basic tech is shown as unexplored, see screenshot.
Obviously, all of it is explored and widely used

I was playing with universal unload for a while, and my solution is to
- make an "unload" station with purple chests
- make lots of "requester" stations for each resource I want, an set limit on them from 0 to 1 when a threshold for a resource is reached; they may be placed in a row on a single rail ...

I've just got auto-updated to 2.0.8 from the latest 1.x release, and now I cant add rails to my existing base where I need it (error is "legacy rail is in the way" or something). Is there any workaround or fix available?
Also I noticed that rail turn radius in now larger, and as I use roundabouts a ...