There is a hacky way to do it. A platform will not drop an item to a planet if it is also requesting that item from the planet. Even if the request is 0.

So, you can make a zero item request for QPs from Nauvis. It's not an ideal solution at all, but it does work.

A value that is deemed by the game itself as secondary


In what way does the game deemed it "secondary"? It seems pretty clear to me at least that cargo bays are meant to increase both storage and throughput. Indeed, the fact that one scales with quality while the other does not strongly ...

Came here to make this same suggestion! With 2.1, I would love to make light-hauler platforms that get their ammo and fuel from space stations orbiting each planet.

But you can do that as is. The only difference is that you'd need 3 chemical plants doing fuel production instead of 2 assemblers ...

+1

There have been so many times when I reached for the green button on the main blueprint page instead of the green button on the parameterization page.

Also suggesting this. Especially for getting rid of extra ice on Aquilo. The current best way to get rid of extra ice is to build a bunch of recyclers to repeatedly recycle ice into less ice. Where does the extra ice go? Is it vaporized or turned into dust? I'm pretty sure Aquilo is too cold for ...

+1 on making spoiledness priority apply when taking from belts. I made a lot of designs on Gleba that never quite worked right because I had assumed that it did apply.


How would that work, exactly?

Let's say that you have it set to least spoiled first. There are 2 stacks on the belt, and the ...

I cannot trigger the "Go to [cargo-wildcard] Station" only when the "destination is not full" becouse the train has to be in "waiting for space in destination station" to take advantage of the station priority and dispatch the train from the station with highest priority.


This works for me on ...

Just treat Space platforms as secondary storage chests and I would be 100% happy. Because now I can just put my mall into space and not buffer several of every item on each planet in case I might need it. Instead, when it's needed it will just be sent down. Similar to how item are getting sent up ...

Note that with 2.1, value parameters that get orphaned by removing the entities they affected from the blueprint now can stick around, so long as they're being used by other formulas.

So it'd be really nifty if we had a convenient way to *create* such values. You know, without having to add an ...

I ha
I see a lot of nests that are very close to your farms. You're researching railgun stuff, so you're definitely post-Artillery. Have you considered using some on those nests?


I have certainly considered and would like to do that. But you will note that both rocket and railgun turrets ...

I see a lot of nests that are very close to your farms. You're researching railgun stuff, so you're definitely post-Artillery. Have you considered using some on those nests?

In 2.0, there was a semi-common bug that would cause pentapods to just stop expanding. They had available chunks to expand to ...

I have to manually recreate every interrupt that is even slightly different between the two groups. For instance I might have an iron train group and want to make a copper train group, or I have an item train group and want to make a fluid train group.

I really feel like blueprint ...

Is the alert actually tied to radars specifically? Because it might just be "if you have vision over a chunk when biters expand, you get an alert." At which point, radars are no longer the way to control this.

Now that 2.1.13/14 have been out for nearly a week, what's the thinking on biter expansion at the present time? Is it still too strong, or is it fine now?

"Transport belt capacity 2" already increases hand size for noral inserters 3 -> 4

Note that this is mostly so that you don't have regular inserters leaving partial stacks all the time when taking from stacked belts.

Right now chest-to-chest (trains/assemblers) item transfer is more efficient ...

Because these interrupts already exist on other ships

When you say that the interrupts already exist, do you mean that an interrupt with the same name as the post-parameterized interrupt already exists? That is, in your example, your blueprint has this as the name of the interrupt:

-> <param0 ...

P.S. Oh and defending Gleba feels pretty underwhelming when you visit it as a last planet even on DW 600/600, the attacks barely scratch me (even while continuously producing something like 600SPM). Wish there was some sort of internal modifier for gleba enemies' aggressiveness that'd go up based ...

I don't think this is a throughput issue per-se. Or at least, not in the way you mean.

The steam pipe segments consists of 4 pipes, so it can hold 400 steam. One tick of neutralisation generates 10k steam, 400 of which leaves the machine. So the maximum rate of transfer between the machines is 400 ...

Imagine being convinced to try this new game, spend multiple hours learning only to face insurmountable waves of enemies and be forced to restart.


One of the nice things about pollution-based enemy attacks is that they're pollution-based.

New players are way slower at building stuff than ...

Wouldn't it be simpler and probably better to have inserters pick-up from both sides interchangeably? If second side is empty, it will skip it, but only until there is something on the other side. This way inserter may pickup from both sides, while having the priority for the last unused side ...