It seems that currently all simulations (tips-and-tricks, and menu-simulations) have their zooms capped. Meaning you cannot zoom out as far. I'm not sure what was the case in Factorio 2.0, but I remember in Factorio 1.1 there was seemingly no cap.

I assume the cap is in place for different reasons ...

+1

This would be awesome. Many times I've that this would be the intuitive behaviour, since the belts are all connected now.

Klonan wrote: Thu Jun 25, 2026 6:46 pm There is the hard limit, that they won't try to expand to a chunk with any player buildings

So some form of victory poles are still possible? You just need a lot more victory poles

+1

I can only tell they're on route if it's to a unscheduled one, cause then I can see the contrast difference.

An alternative solution would to have a extra tooltip field "Scheduled for build" or something. This is the better option IMO, since it's always clear.

+1

This would be really useful for Space Exploration. Currently we need to place a floating GUI at the right pixel location, including accomodating for the schedule GUI being wider sometimes.

There should be a little window with a search bar next to the schedule window. Pretty sure there you can type the zone name, and it will show you all stops on that zone.

+1

I've lost count about the amount of times I've clicked on an inserters filter only to realize it's not enabled yet.

Maybe related to 127266?

+1

Ran into this many times before too.

Can't you just reduce the amount of ingredients required? Basically, what's the difference between: and

This is a cool idea! A little tricky to implement though because the way electricity works is not very moddable through the API.

I did write this article a while ago that includes some older mods that did similar things. Some info is a little outdated due to 2.0 release, but most of it is still ...

Ah, wait, if you press escape then it goes to character controller, and then you put it back in remote view, so have to press escape again... I see

What

Add a field to ghost build events to gives a mapping between parameters and the signals they need to replaced with. Something like


parameters : dictionary[SignalID → SignalID] : mapping from parameter signal to signal it was replaced with


Will probably be needed for the events: on ...

I could set the controller back to the remote view in an event handler, but I'm sure the player would not be able to access the game menu.


What do you mean with this? I'm quite sure if you listen to on_player_controller_changed and set it back to remote view if the player left it that it will ...

For anyone looking for this in Factorio 2.0+, it's now done using https://lua-api.factorio.com/latest/cla ... ntity.html

Ah I see. In that case I would strongly prefer it being a required field, and not have a default value. For the same reason of keeping it simple. It's an very easy migration for old mods, and very easy for new modders to learn. If they don't add the property the game will error and tell them exactly ...

Option B for sure. I think keeping it simple is easier to understand than a gotcha moment where modders didn't know `additionional_categories` existed.

Sure, new modders might miss that property the first time. But it will be one of the many other properties that new modders will miss while ...

Have you tried ValvePrototype::flow_rate?

Edit: scratch that, that's something else

+1

TL;DR

Add a way to register an a specific entity (or it's control behaviour) to raise an event when the signal input changes (and optionally passes some conditions ). Similar to how register_on_object_destroyed works. Something like:


---Lua psuodo declaration of function to register a specific ...