I'd just like to chime in on the details of how this may be implemented, since I don't beleive making `nil` a meaningful value like this would be good. `nil` in prototypes usually means "use default value" where said default value is a value you could also set directly. Like lets say 0 was the ...

Fyi there's also this post with a little different explanation: viewtopic.php?p=439604#p439604

What

The setting `autosave-slots` does not show in the "The Rest" settings gui.

(It's not in "Other" settings gui, which is very most likely intentional.)

Expected

The setting `autosave-slots` should show in "The Rest" settings gui.

Note

Just a sanity check: the setting does work when ...

Based on this I recognize a pattern that is probably relevant: in LuaGuiElement.add the entire structure gets converted to a PropertyTree first, including the localised string. Assigning to LuaGuiElement.caption doesn't do that, neither does game.print, neither do most things (edit: that take ...

Now knowing that it's property tree related I've done more investigating and this behavior applies in 3 cases (see https://forums.factorio.com/viewtopic.php?p=560285#p560285 ).

And for anyone finding this through search, you can actually set LuaGuiElement::caption to a LocalisedString containing ...

LuaProfiler says "They can be used anywhere a LocalisedString is used." However there are 3 locations I found where LocalisedStrings are part of property trees causing this to not apply (meaning LuaProfilers are not usable). I'm pretty sure I've gone through and tested all data structures that can ...

I see, that makes a lot of sense. I will simply ask for a note about that on the LuaProfiler page, since the reason why I thought it was a bug was because LuaProfiler says "They can be used anywhere a LocalisedString is used."

I'll make a post in https://forums.factorio.com/viewtopic.php?f=28&t ...

What
When trying to assign a LocalisedString to LuaGuiElement::caption that contains or is a LuaProfiler it errors:

Value must be a string in property tree at ROOT.caption[...]

Expected
I would expect it to accept the LuaProfiler and show its elapsed time/duration. On save load I would expect ...

The description for `scroll_mode` for LuaGuiElement::scroll_to_item mentions "scroll-pane", contrary to the function's (correct) description saying "listbox".

The description for `scroll_mode` for `scroll_to_element` seems to be identical, it is correct in that case, just make sure to not break ...

According to my tool there are 0 (latest 1.1 releases of) mods on the portal with `unlocked-recipe` in any of their .lua files, and I believe this to be accurate.

While I agree that keeping docs up to date is important, and adding a notice in the changelog is good as well, I am incredibly happy to ...

Oh good point, it's not addressed in regular Lua. I'll see about reporting it to them, though I'm far less confident reporting to them.

Regardless, if it is addressed in upstream Lua, I will let you know

What
When Lua tries to get the debug synbol name / varname for a register it crashes if that register currently has a "local" name that is `NULL` (or 0 or nullptr, whichever you prefer).

Expected
I'd expect Lua not to crash, and I believe it is because this function assumes that all varnames ...

We have done some profiling as a group effort in the discord and have noticed that by far the slowest mod in this case is fCPU.
You can see the report for details.

As for what you can do... well
Removing the mod, trimming and then adding the mod again isn't really an option.
So, unless i'm terribly ...

tyvm

When ghost dragging substations next to unpowered entities the substation ghosts get placed too early/close to each other resulting in coverage overlap.
Example.png

Reproduction
Place entities like steam engines or assmeblers in a row, for example using this BP ...

Nice! Really wasn't expecting a fix so this is a happy surprise

Note

First of all i'm just reporting this to explain how it happened so you aren't confused by the auto uploaded crash report. I personally don't consider it fix-worthy. The ultimate reason it happened was because i had to create my own `base` mod in order to create a new save using `--create foo ...

Great to hear!
I've since written a script to make other cases reproducible which seemed timing related (which are actually cursor location delta related), but i shall wait until next release to see if those have also been fixed

There are several cases where smart belt dragging ends up placing belts on the incorrect row or column or the belts are facing the opposite direction. These are just 3 cases i managed to reproduce.

Syntax:
starting with belts facing north (^)
. = start
^ > v < = move cursor one tile in that ...

Alright, well it's a mod now: https://mods.factorio.com/mod/WiderNoticeTextBoxes
It being a mod doesn't really achive what i was hoping for, but hey if people like it they can have it now.
If it changes in the game itself i'll just deprecate the mod.