You could even set a wait condition for passenger present and use the and operator with it and passenger not present. This means that the space platform will only leave when you tell it to (by clicking the travel button). Even better, you can add an interrupt which never fires automatically (which can ...

This is just the same point like with trains: a "condition" that switches the train to manual mode. And all these "workarounds" are simply more tedious ... a "home station". Not just that I have to combine two conditions like "passenger present AND passenger not present" to keep it there for the time being ...

... rainbow effect on them.

Bugfixes

[space-age] Fixed that victory condition didn't trigger when the platform was paused or didn't stop at solar ... removed. (https://forums.factorio.com/123751)
Fixed cargo pods with passenger would select landing spots using incorrect bounding box. (https ...

I'd like to see this revisited and considered for space age as a condition on space platforms. At least with space platforms you could at least allow for reading the number of characters in the hub (there is a character signal that could be output with the number being the number of characters that ...

... schedule be "Go to Test - Hanger." Then just add your one interrupt: Passenger present => Go To Test - D1, Wait Condition: Passenger not present.

That should give the results you are expecting in your example.

... with a station stop set for another planet that it's not at
2. Add "Passenger present" wait condition
3. Make sure passenger is not present
4. Flip the selector to Automatic

Expected Result:
Ship does not leave

Actual result:
Ship blasts off for the stop

Windows 11, Steam, latest stable

... reached the Solar System Edge with my ship and noticed, that the win condition trigger is a bit confusing:

Observed Behavior:
I flew straight to ... the meantime, I personally wrongly assumed, that I would need to be a passenger on the ship in order for the win condition to trigger.

Expected ...

... still haven't implemented this. They've done so much work on the rails but never implemented this obviously-needed feature which I'm sure almost everyone wants at some point.

I use "Passenger present" AND "Passenger not present" as a hotfix.

I wouldn't hold your breath on a proper implementation.

Add the condition "passenger present"... or absent if you're on board.

... Count" it might be worth using stricter and consistent naming of Wait Conditions between the "Picked List" and "Selection List"
Especially now that ... Item count | Cargo {{ condition }} | ❌ Major, shorter, mismatching |
| Passenger not present | Passenger not present | ✅ None |
| Passenger present ...

... going "no, this can be fixed from the map view". About 600km in a race condition meant a chunk of landfill didn't get built and it was a great relief ... the "engineer's train", which runs between here and the main base on Passenger Present.

I'm not sure what to do next but it will not be building a ...

... the rail block contains a manually controlled stopped train with a passenger -> Add a penalty of 2000.
When the rail block contains a manually ... that can cause a train to repath listed below. When one of these conditions is met the game considers possible paths from the trains current ...

... at signals.


They do fire when sent to a tempory stop with the condition changed to "inventory empty."


They will from manual mode, too.

But ... I would agree with this. The current design is ok for light passenger rail, but it would not support heavy freight ...

... e.G. after refilling mats).

Schedule parameter: Please add to the conditions list the parameter NOT like in "Passenger present" and "Passenger NOT present". The reason is simple, a train may not be FULL but also not Empty so you have to work with circuit conditions which is on scale sometimes a ...

... work. If you don't want a stop to be skipped, you add one of the conditions like time passed or inactivity.


Such is valid. I mainly suggested ... by just having a zero second wait condition.


I would include passenger present/absent as being not known - how can you tell if the passenger ...

... should skip a stop it is set to skip if it already fulfills the wait conditions of that station right when it is departing.


Background:

A few ... longer fulfills the skipped station's wait conditions during transit (passenger jumps out of the train, someone steals or places resources in the ...

... of an item in a chest near the train stop, which would make the passenger train wait at every PAX selected as temporary stop with the current ... is also possible to have a fire and forget behavior if you change the condition of the train after you clicked for a temporary stop to something that ...

If the current no condition behaviour is retained, but "switch to manual" was added as a pseudo-condition, the only difference in action would be the ... clicks if counted literally.

It seem to be faster to instead select "passenger present" AND " passenger not present", although that is adding 2 ...

What do you see as the benefits of the current default "5s passed" condition for temporary stops vs "Switch to manual"?

The only thing I can see you described (in this thread at least) is that you can add a condition to additionally require passenger present, to get behaviour that the train waits ...

As I told I could also add a new train stop, and the condition "passenger present AND passenger not present", but it's annoying because every other current solution than this "Stop"-"condition" means much more clicking.


The only way to save clicking is for the behaviour when there are no conditions ...