https://lua-api.factorio.com/latest/types/LightningProperties.html#exemption_rules

if you set/keep them at nil the game loads up just fine, this leads modders into a false sense of security that they don't have to check if the array exists first.

so it would be nice if they were both marked as ...

The installed tab shows it localized, whilst the updates tab shows the raw mod name. (the two planet ones are sticking out like a sore thumb)

When GuiAnchor was implemented ghost guis weren't a thing yet.

When you use name or names as a filter it'll stop appearing on ghosts even if they share the name, which would require the player to just listen to the gui opened event of that gui type in general and then manually toggling it, which is ...

Currently it only remembers it if its the latest played world, i.e. the one shown on the big green button on the menu screen.

Whilst playing online i have to occasionally drop into a local save or just save the server's world to test some stuff, and each time you return you'd have to re-enter the ...

- try to open a world
- open the sync and load mods gui
- press the sync button
- uncheck the "load save after sync"
- wait for all the green bars are full
- notice the game restarting and then loading the world

expected behavior: for the checkboxes to either still "work" after clicking the sync ...

Forwarding this here since it got confirmed as a bug, and so i can link to this issue from the elevated pipes mod.

+1

It currently has no description, it would be nice if it was documented that this is what controls which entities can freeze or not.
https://lua-api.factorio.com/latest/pro ... ing_energy
https://discord.com/channels/1396775903 ... 7697374328

isn't the difference generally that one is integer and the other one decimal?

TL;DR
It would be nice if recipes that are disabled due to lack of fluid connections say so in their tooltip, just like recipes restricted by surface conditions.

What?
Something like "Cannot be crafted in this machine. There are not enough fluid ports.", but a little bit more snappy than that ...

Wow that's quite out of sight near the bottom and in a normal font, not used to read the on_load documentation since i know what the event is for, it might be worth moving it to a more visible spot, like right below the lifecycle diagram in a noticable color

I'll post it in documentation improvement requests since it seems just ever so slightly more suitable than calling it a bug due to the lifecycle diagram.

So lets start with probably the most common usecase, tracking data for any/all surfaces within your own mod, this is typically done by going over ...

Recently we got some new inventory defines like crafter_input in favor of furnace_source & assembling_machine_input, it would be nice if the "deprecated/old" ones were marked as such, with like a strikethrough or in the text description afterwards, something like this perhaps:

Also i found it quite curious that the default custom status for merely container prototypes was added just to support the crash site, i wonder why it doesn't just set the custom status via script as it generates the crash site since i can hardly imagine when someone would want to set a data stage ...

There's no way to tell without using the prototype explorer which ones reset their freshness and which ones inherit the spoil timer.

In remote view you can ctrl click modules into an assembler before setting a recipe, when you set the recipe it yeets them even when they're compatible.

Did not check any of the other 4 orientations and each of the 4 wire connections it can have, but you can clearly see the shadow reaching over the combinator:

When you disable a rocket silo by script it'll still allows the silo to receive a new robot delivery order as well as trying to launch when in automated mode.

In alt mode you can see that in both instances the items move to the cargo pod of the rocket but then it just stays there, and the platforms ...

Can't it crash to the menu instead of violently exiting the entire application?