Thank you! This one bugged me, having to zoom out to change the schedule.


Note, the fix is to not show the hotkey tooltip when zoomed in since the controls specifically are setup to disable themselves when zoomed in.

Oh darn. I guess that's better than nothing. It would be really nice if ...

Thank you! This one bugged me, having to zoom out to change the schedule.

This a good case of ambiguous user intention. There are good reasons for the user to want either red or yellow undergrounds. The game should not try to guess which, and should instead try to make it obvious to the player what they need to fix manually. The current behavior does a decent job of it ...

is it impossible?

https://mods.factorio.com/mod/cargo-ships

only would replace ships in tugs with platforms

https://www.anno-union.com/wp-content/uploads/2018/06/AnnoUnion_ShipVote_TugBoat.jpg


Cargo ship maintainers here, many things are possible if someone can help us with the sprite ...

+1

Maybe instead of "unset", is could say "nil (auto detect)"

I got beaten to the punch but here's my response too.


I have copied this string from a Reddit post, but I don't understand what's going on.

The OP (fofz1776):
https://www.reddit.com/r/factorio/comments/mj6a20/sushi_made_simple_how_to_make_sushi_the_easy_way/?rdt=54092


0eNrlW+FymzgQfhd ...

What I actually need is a user interface I can use in my mod to build compound objects, with collision checks and all this stuff. Maybe it already exists, and I just don't know about it?


You can always hand code placement visualizations that only appear when the players cursor stack is your ...

There are other collision layer names that have special purposes and don't actually cause collisions to happen, like elevated_rail_support. It would be nice if these special cases were documented somewhere.

https://lua-api.factorio.com/latest/types/PipeConnectionDefinition.html#underground ...

There are other collision layer names that have special purposes and don't actually cause collisions to happen, like elevated_rail_support. It would be nice if these special cases were documented somewhere.

In that case, definitely take a look at the source code for Honk! It has a good system for playing sounds and identifying train events. You could probably make it work for you by cutting out all the options and changing the coordinates where the sound is played.

Because it's deterministic, though, you should be able to predict what inputs will be processed in what order. Or even barring that, a machine could guarantee that its input went first or last in the processing order if there's sub-tick timing involved by just spoofing its input timestamp.


I ...

As long as recoil and spread is deterministic, it can be defeated by perfect input. And again, hiding gamestate is a fundamental departure from deterministic lockstep that Factorio uses.


That brings up another interesting point. Factorio is deterministic *for a given time sequence of user ...

You are getting the error on line 42 because it is trying to read the ingredients tables that you added on line 31. You added them with "type" as a named field in the table, but name and amount are given positionally so they are actually [1] and [2] respectively. You need to specify them as "name ...

Interrupts only trigger after the wait conditions of the current stop are satisfied and the platform/train needs to decide where to go next. You will need to add an extra condition to your Aquilo stop that says "OR fuel cells < 10" so that it will leave Aquilo at that time. At which point it will ...

Does it happen when driving it normally in game? I see your screenshots are in editor mode, which makes some things go wonky sometimes.

I understand now, thanks. So the workaround might be to put the Depot in the permanent schedule twice so that the fuel interrupt runs in between them.

You don't even need to download and modify Honk. You can make a helper mod that has Honk as a dependency and changes the sound files. There's even an API to change the sound only for certain types of locomotive. I'm happy to help if you have a specific idea for when it should play.

Ah, I missed that part of your post, sorry.

It seems like in your case at least, the current behavior is actually helpful, right? If an interrupt fired after it departed the temp rail stop and before it went to the temp provider stop, then after the interrupt finished it could go to a different ...

How does the "Interrupt other interrupts" setting affect this behavior? Is this a symptom of the logic assuming every temporary stop is an interrupt stop, instead of reading the "created_by_interrupt" flag?