Space platforms with satisfied departure conditions should stop queuing rockets to fulfill requests

[kaijyuu]

Currently space platforms will wait for rockets to arrive before they leave (this is fine) but they will also keep requesting more rockets even if all the departure conditions are met (this is not fine).

Easy way to show this:

Set space platform to a simple departure condition like "wait 10 seconds".
Set it to request some item in large numbers that the surface can provide.
10 seconds will pass, but the platform will never leave since the surface keeps sending up rockets.

It's not hard at all to imagine scenarios where you might want to request items if convenient but not care if it's completely filled before setting off. In fact I feel this is probably the more common case; if you actually care about your requests being fulfilled before launching, you'd put it in the departure conditions.

[Tinyboss]

The point of "all requests fulfilled" is to keep the platform there even if the planet cannot satisfy the request. Not having it means "you can leave if some requests CANNOT be fulfilled".

I honestly never considered a situation where I'd want my ship to leave if it has requests that can be fulfilled right now.

I'm not at all against making that possible! But changing the meaning of the requests satisfied condition isn't the way.

[Sworn]

Yah, so you are more concerned about time then the actual fulfillment of the request, which can be an important factor for items that will expire.

What one would expect is that, if I set it to 30seconds, after 30 seconds, it would stop sending the logistic request to the planet. Of course, it would wait for the rockets that were already in launch progress but would cut the logistic request.

The point to understand is that it would only cut the logistic request, when the platform want to leave, like you said, 10sec or whatever.
If one doesn't want the platform to leave, the wait for all requests to be fulfilled is the option.

I would say it is perfect reasonable to behave like this.
Like a train can leave immediately after the condition on its schedule is completed, regardless of how the inserters are adding items or not.

Would be a little wasteful if the station departs with rockets middle way, so it waits, but it doesn't cut the request signal, which make it never leaves if you find yourself in a state where a rocket is about to land, but another is starting to get out. Which is exactly the point of the original suggestion

[Molay]

The point of "all requests fulfilled" is to keep the platform there even if the planet cannot satisfy the request. Not having it means "you can leave if some requests CANNOT be fulfilled".

I honestly never considered a situation where I'd want my ship to leave if it has requests that can be fulfilled right now.

I'm not at all against making that possible! But changing the meaning of the requests satisfied condition isn't the way.

I can tell you have a situation where the current behavior is very negative. I have one (huge, but doesn't matter) ship that flies out to aquillo. Among other things, it drops the materials to make quantum chips, and also picks up quantum chips.

So what happens is, I drop the resource, quantum chip production starts up, about 15 chips per second. My platform has exceeded it's wait condition, but can not leave until all quantum chip requests are fulfilled, because quantum chips trickle in fast enough to constantly launch a new rocket before the previous one made it's delivery.

It could be remedied with smaller quantum chip requests, but ultimately that is impractical, because said platform has varying route times, because sometimes it flies out towards the shattered planet for some time, at which point it makes sense to have a higher request for quantum chips when it returns to aquilo.

If the platform would just stop requesting new launches after it's wait conditions clear, it would depart as expected. Currently, it can literally get stuck for a long time.

I wouldn't change the all requests fulfilled condition either. But if I have a condition of say time passed 300, I want the platform to get ready to move on after 300 seconds, after the last launches-in-progress are done, and not request a new rocket every 14 seconds or so when items become available.

[myridium]

I consider this a bug.

Your suggestion is clearly the correct way to do this. It's not a wait condition if it's just ignored anyway.

[Sworn]

+1