... stop have lower pathfinder cost regardless of priorities and the behavior would still happen. Problem in your setup is that you are using Exit waypoints which the train reaches while still being in the Enter train stop block. There is a feature to prevent rail stackers from being overfilled, which ...

I was looking at how the foundry did the sound waypoints I remember hearing in a FFF. Just to see if I could somehow piggyback off that system to do smoke (doesn't look possible).

I noticed that the base game defines an `audible_distance_modifier` on the SoundAccent s it provides, which is missing ...

... schedules here, but about temporary train stops.


Trains in Factorio have never worked this way. They don't add stations themselves as waypoints, and they don't spontaneously reverse direction.

However, you can add the station to the train schedule yourself with no leaving conditions, and ...

In Factorio 1.1 when overwriting the cutscene controller with new waypoints, if the first waypoint had `zoom = nil` then the zoom value from the previous waypoint would be used. In 2.0.11 this behavior has changed, so if the first waypoint has no zoom the camera will go way in.
I assume (and hope ...

... entity
/c character = game.player.character
-- start a 7 second cutscene
/c game.player.set_controller{type=defines.controllers.cutscene, waypoints={{position={0,-10},transition_time=300,time_to_wait=120}}}
-- access the character's opened field (using game.print so parses as valid Lua)
/c ...

... call it "FHack", since DFHack is seeming like the correct architecture to follow. "Compilatron Therapist" would be the utility that lets you edit waypoints or a to-do list for the automated client. If these applications have a REST API or web interface, then that would be a great dividing line ...

I can reproduce the same error message by waiting for the code to run (including choosing waypoints), and then use /editor to add a bunch of water on/near the waypoint.

Here is a save that will reproduce the issue (game.print is called with the coordinates of the stuck unit group when it happens).

... suggestions/feedback about how I could make progress (if there is more debugging info that would be helpful). Perhaps our algorithm for choosing waypoints could try harder to find a location farther away from water, for instance.

I guess maybe an option would be to destroy the unit group, and just ...

... suggestions/feedback about how I could make progress (if there is more debugging info that would be helpful). Perhaps our algorithm for choosing waypoints could try harder to find a location farther away from water, for instance.

I guess maybe an option would be to destroy the unit group, and just ...

... for the most :P

First, a shameless plugs: https://forums.factorio.com/viewtopic.php?t=104721 and https://t3st3ro.github.io/stuff/factorio-waypoints.html
and requests directly related to that:
Could you add some API for registering a bunch of actions as a single entry on the undo stack ...

... one object to another. If you store it as a hash table where the key is the endpoint and the value is the estimated time to make the trip (and waypoints along the trip if necessary, like if it's too far to get there without charging). Only add entries when the hashtable does not already contain ...

when I set a new waypoint right around the time an autosave is triggered. The already set waypoints get discarded after the autosave finishes. If I quit the game and load the autosave the waypoints are still there

This is constantly happening to me too. Steps to reproduce: shift click to enqueue/chain waypoints for a spidertron on a map and when the autosave is triggered around the moment a next waypoint is being created the entire chain gets cancelled after the autosave finishes

Are you saying it is ...

This is constantly happening to me too. Steps to reproduce: shift click to enqueue/chain waypoints for a spidertron on a map and when the autosave is triggered around the moment a next waypoint is being created the entire chain gets cancelled after the autosave finishes

... I have a red spidertron with the white and green spidertrons set to follow red. I grab the remote for the green spidertron and send it to several waypoints, holding shift the entire time. After it reaches the last waypoint it returns to following the red spidertron. I grab the remote for the white ...

... I check whether the path end rail has changed since the previous tick. If it has, that's because the braking point passed a scheduled stop. I use waypoints so the trains don't brake, they just go right by, which means the recorded distance is as close as the train got before its braking point passed ...

... I check whether the path end rail has changed since the previous tick. If it has, that's because the braking point passed a scheduled stop. I use waypoints so the trains don't brake, they just go right by, which means the recorded distance is as close as the train got before its braking point passed ...

... lengths, but as a way of validating models I thought I'd measure throughput as directly as possible.

So I put a train on a long oval loop with waypoints at the end of each straightaway and watched for the train's path_end_rail to change. Each tick I recorded the distance from the train's back rail ...

... trains not fitting in it to stay at their departure location with the "destination full" message. They would choose the other Elevator (name 2 "waypoints" the same) that has still some room left, even if it's not the closest though.

The other points you mention are indirectly related to the limits ...

... and dynamic obstacles allows this. There's no need to check every tick if something got in the way. In fact, the new queueing system literally is waypoints!

It's not static, though. Any roboport at any given moment could be destroyed or deconstructed.


There's no reason this needs to be handled ...