Launch Inactivity [Spaceship wait condition]

[Saevon]

TL;DR

[X sec Inactivity] check for incoming/outgoing rocket/dropod launches to spaceship scheduler

• (also) rename "inactivity" to "hub inactivity" for clarity.
• OR just make "inactivity" this new form!

What?

When you have multiple requests or providings on a space platform, but don't expect all of them to finish — you might want to check for "launch activity", so the spaceship waits as long as stuff is being sent/taken from it. This timer would reset on a droppod-launch or rocket-launch.

• Currently "Inacitivity" un-intuitively checks for the "hub" activity AND rocket activity: So if you have a ship crafting using the hub constantly, it can no longer fly off when the planet doesn't need it.

This differs from "request satisfied" as the goal isn't to have fulfilled everything to max; but to detect "inactivity from spaceship to the current planet". Same way "train inactivity" is about "inactivity from train to the station".

Alternatively: Changing the existing "inactivity" check to remove hub interactions from the rocket; I don't know if a "hub inactivity" check is actually useful, as inserters can already be wired to "read hand contents" to check for it.

Why?

This provides consistency and thus intuitiveness between the way you use "inactivity" for trains and spaceships. Scheduling generally deals with "station to train" logic. It also provides something unmoddable (afaik).