The old topic's name is not very good. What are these localised strings supposed to be added for? Dropdown already takes an array of them for item names. It shouldn't require reading the first post to tell.

Mod settings can already have dropdowns with tooltips, just expose this ability in LuaGuiElement.

For https://forums.factorio.com/viewtopic.php?p=600414#p600414 I made separate union types for the alignment and added these descriptions: firefox_LrZqpS5yPb.png "The text is at the given side of the target position" is the exact opposite of the actual behavior. The elaboration is correct...

Pi-C wrote: ↑

Sun Jan 07, 2024 12:21 am

The beauty of this is that this will also give you the number of filtered slots if you use '#returned_list'.

What would you want it for?

Pi-C wrote: ↑

Sat Jan 06, 2024 7:51 pm

So perhaps the method should return an array of "{ filter = string, index = uint }", or even simply an array of "{ string, uint }" instead?

Why do you want it to be an array so much?

That's a good idea! But I've a question regarding the bots' job queue: Do they get assigned to pick up items from a certain logistic chest, or from a particular slot in the its inventory? In the first case, they'd still get the item if there are several stacks of it, but in the other one, they'd re...

FWIW, you can still do your thing in one pass. You just have to check the chests and manually move the trashed items if they can satisfy your request. E.g. in your example you would trash 200 copper in one tick, then in the next you would bring them back into the filtered slots and request 100 more,...

It's a table where you can select rows like in a listbox. Example can be found in the multiplayer game browser window. This kind of table being available will be a massive improvement for mods. Right now any mod that wants even slightly nontrivial functionality from a listbox is forced to roll out i...

Sorry, didn't notice that. Yes, it should be in the event description, since it's the property of the event and not merely how it was raised. You can operate on the stack directly to change it and that also raises the event (and isn't mentioned anywhere, AFAICT).

Properties marked as can be nil when they can not. Type-specific properties are not marked by the customary "Can only be used if this is <type name>" or lack any note whatsoever.

IDK when it is raised, but it should be pointed out in the docs that it's not immediately.

I am sure it's not just me who finds player.selected an invaluable tool for quickly inspecting entities. But when I work on GUI, time and again I find myself missing this ease of access. If I could simply point at an element and access it in code, that would be extremely convenient.

FFF 388 announced engine support for ticks up to 2^64, but only Lua support for ticks up to 2^52. We can work around the Lua limit by breaking up the tick into two 32-bit numbers. The upper 32 bits are easy to calculate from LuaGameScript.tick. But we need a new property that contains the lower 32 ...

Excluding "productivity" from allowed_effects just controls productivity modules. We already have it set to reject those. This doesn't stop the entity being affected by mining productivity research. That seems like a bug to me. Mining productivity bonus is a productivity effect, I think i...

What if you made the miner reject the productivity effect? It's not like productivity makes any sense in an offshore pump. Would it ignore the mining bonus then?