Indeed, the method doesn't support that argument: https://lua-api.factorio.com/latest/cla ... s_filtered

Done for the next version.

In Built-in constants , control:temperature:bias and control:temperature:frequency are missing. They are used in temperature , which is used for tree placement. Weirdly, they also don't have associated controls in the UI either.

In Built-in functions , expression_in_range function is missing ...

I've updated the docs for the next release.

Thanks for the note, this is fixed for the next release.

From what I can see in the code this should already work. The variation of the sprite is picked based on the tier of the module. Are you sure that the tier is set correctly on the module prototype?

For the UK residents:

It changes the actual area. You can also read it runtime via LuaEntity::mining_area.

Thanks for the report, fixed for the next release.

You can read it through radius_visualisation_specification::offset.

There are a lot of instances of fuel pollution in tooltips, what prototype is this one?

You can use on_surface_deleted and on_surface_cleared for surface deletions or calls to LuaSurface.clear.

Thanks for the detailed notes! I've adjusted the docs for the next doc release. I've also added LoaderBlueprintControlBehavior:

The keys for the dictionary are defined by the documentation. It's "the names of all prototypes of this type". What prototypes of that type exist depends entirely on what prototypes your mod and any other mod in the game have created. If you want to find out what prototypes are in your game with ...

I've updated the docs to be clearer for the next doc release.

And the rest is fixed for the next doc release (newer than 2.0.70).

Please make a new bug report with reproduction steps, exact game version and so on.

LogisticSection::active fixed for the next version (2.0.70), rest still pending.

Thanks for the note, it's not optional, doc fixed for the next version.

The section as is on logistic network would be a bit too short to make its own page, but if you can add more information (like the behaviour with multipliers, maybe something from the FFF) then that sounds like a good idea to split out.