Because requests don't have a priority system.


Check this out :

Say you have 10 000 bots in your network. Request 12 000 in mall , and voila. The bots will show up on the mall , and nowhere else.

But i have 2 malls !

Easy , request 6000 in each mall.

No i have 10 malls and when i ...

Of course, doing this means you can't use bot request for what they're actually intended for, i.e. making bots go to particular place. Got a mall and want to make sure the roboports near it have lots of construction bots in them, ready to pick up items and head off the moment you slap down a ...

+1

I've never been able to figure out exactly what the rules are for when it will or will not automatically place ice platform, concrete, or both.

Edit : Say you have 1000 roboport in your base, you could have up to 350 000 robots in them, but that would be very bad, they would lack charging capacity for a significant % to be active, and they would never find a place to rest. But if you have 35 000 bots, then it's fine, you have on average ...

*sigh* Yes, you can do it with the current circuit options. I did eventually get it working (modulo it sometimes buffering a couple more U235 than strictly needed) myself. I'm sure all you Very Smart People would have instantly seen this correct setup, and not gone through a couple iterations that ...

Ranakastrasz wrote: Sun Sep 06, 2026 5:50 am Admittedly, you would then have to ban all robot types then.

Unless mods are involved, that's just 2 requests: Logibots, Any quality, Max 0, and Construction bots, Any quality, Max 0.

+1

It appears to me that when you do a kovarex enrichment, you want the centrifuge to run 100 % of time, and for this you just need to have them with a buffer of 80 "good uranium". When crafting that will represent 40 already loaded for next craft to make sure no delay, and 40 being used as ...

So, the downside of this is that it could potentially cause a lot of annoying and wasteful back-and-forth. Let's say you've got your iron smelting area set up to load 1k iron plates into its buffer chests. A ship comes in requesting iron plates, so it the request is assigned to a silo and bots ...

It appears to me that when you do a kovarex enrichment, you want the centrifuge to run 100 % of time, and for this you just need to have them with a buffer of 80 "good uranium". When crafting that will represent 40 already loaded for next craft to make sure no delay, and 40 being used as ...

In 2.0, the way higher-quality modules worked was that their positive effects are multiplied by the +30%-per-level quality bonus, then rounded down to an even percent (or tenth of a percent in the case of quality modules). This resulted in some qualities of some modules being substantially worse ...

I'd prefer that platforms simply couldn't get stuck this way. If a rocket silo thinks it can handle a request, but then fails to do so (insufficient items are available or whatever), the request should be aborted and the platform should be free to leave.

So, the downside of this is that it could ...

TL;DR
Space platforms which have met all their departure conditions should only wait for rockets that have actually launched, not those that are being loaded; there should be a separate, explicit (and thus optional) departure schedule condition that waits for rockets that have been requested but ...

+1

If I'm pipetting a recipe, it's because I want that recipe. If I wanted its output, I'd pipette the output slot of the machine the recipe is set on.

Note: this doesn't apply in cases where the recipe is a hidden one with the same icon as its output, e.g. electrolyte . In that case, returning ...

That is, in fact, exactly what I wanted and suggested with respect to fuel! Now we just need separate checkboxes for reading inputs, outputs, and trash.


It's actually not needed for any of the use case you mentionned though and there would be no way to read 3 distinct value from only from 2 ...

TL;DR
The special deconstruction-planner-only signals ('Item on Ground', 'Entity Ghost', etc.), currently default to normal quality, and thus only affect things of normal quality . They should instead default to the 'Any' quality so that they affect everything.

What?
Deconstruction planners ...

TL;DR
Currently, ag. towers plant and harvest in a seemingly random order, thus wasting a ton of time moving the arm from spot to spot. Instead, they should go to the closest valid spot.


What?
Currently, if an ag. tower is looking to plant a seed and there are multiple valid, empty planting ...

+1

+1

+1