Hi there!

Wanted to add that it seems like there's a more general issue with "control_up" in simulations. I have another example where the simulation calls


game.simulation.control_down { control = "mine", notify = false }
-- ... some time later ...
game.simulation.control_up { control = "mine ...

The docs for get_widget_position don't really give you much. The arguments are called data and data2, and there's no explanation on what they mean (for each type). Only source of information I can find are files like tips-and-tricks-simulations.lua but only certain kinds of examples are in there ...

Yeah, there are several elaborate workarounds like that that I can do, but I asked because they're kind of unreasonably complicated, and it's just kind of weird to allow load() (which also can override the environment) and not loadfile(). To be honest if load() hadn't been allowed I wouldn't have ...

require doesn't take an environment, it always loads the module with the current environment/globals. In my tests I need to control the environment, so that I can replace things like "game" and "script". loadfile (and load) have an optional third parameter that is the environment to load the module ...

I'd like the Lua function loadfile to work, with the same restrictions as require and load (starting at mod root, not in event handlers, etc., only in text mode, only with .lua extension, etc.). I would be OK with an extra restriction that prevents loadfile from loading files in other mods, if you ...

Summary: When trying to "use" a custom selection tool in a simulation, it's possible to start and drag the tool, but "releasing" it does not work.

Repro

Option 1:
1a. install the attached mod in bugrepro.zip

Option 2:
1b. create a mod with the following data.lua


data:extend {
{
type ...

Thank you, that's one less hack I have to maintain I'll let you know after .46 is out if I still see missing events.

I just noticed on_player_cursor_stack_changed isn't raised in simulations. I could imagine this being intentional (to keep simulations fast/easy to implement) but my mod's behavior depends on it. I can usually fake it, so it's not a blocker, but it would be nice to have a list of events that don't ...

LuaSimulation.get_slot_position takes a slot_index. The game interprets this as 0-based (i.e. the first slot in the inventory is slot_index 0). It means it's inconsistent with functions like LuaInventory.find_item_stack which returns a 1-based stack index.

Intentional? If yes, please document as ...

In my experiments it seems that LuaGuiElements under screen do not respect the location property in simulations. They are always displayed at the top-left, as if location was { 0, 0 }.

Is this intentional or am I mistaken? If intentional, could you please document it ("this has no effect in ...

The official way to tell if you're in a simulation is game.simulation . Unfortunately, game is not defined yet while control.lua is first run, so it's seemingly impossible to tell at that point if we're in a simulation or the real game.

Could you add some way to tell we're in a simulation earlier ...

But the description says this modifiable. If it says "I consumed a Foo" and I modify it to "no, actually you consumed nothing", then it should have some effect, no? Perhaps I was overly optimistic about it returning the item, but there is no documentation on what this modifiable inventory does when ...

The 2.0 changelog says:


Changed on_built_entity event. Instead of stack/item, it passes consumed_items - modifiable stack of items used for the building.


Sounds great but I can't figure out how I'm supposed to use that. I am trying to "refund" the item used when placing the entity. Ideally the ...

Ah, I have a simpler idea that perhaps is easier to commit to.

Could you document/commit that when there is an event "X changed", then you cannot see the new value of X from Lua before the event has fired ? Put differently, which events are instant, no matter what causes them (Lua or the engine ...

Thanks, Bilka!


For events where there are ordering expectations they are documented on the lua actions that raise those events. E.g. https://lua-api.factorio.com/latest/classes/LuaControl.html#begin_crafting instantly raises on_pre_player_crafted_item and at some point in the current tick on ...

A single player action can create multiple events, for example on_player_cursor_stack_changed and on_player_main_inventory_changed. Could you document what to expect in mods about this order?

a. "No guarantees whatsoever": the events can be raised in a different order every time, even for the same ...

So I guess if it counts as "personal use" or "distributed as part of your mod" and not "commercial use", it's ok.

I'm not sure about github, but uploading your modified version of util.lua to the mod portal is ok according to that.


Personal "use" definitely doesn't cover distribution, but yes ...

Sorry, this isn't exactly a modding interface request.

I would like to propose that you license util.lua under a permissive license like MIT. This will enable mods to copy and modify (parts of it) freely, regardless of their license.

My use case:
I am working on a mod where most of the tests can ...

But if you don't want it to be auto placed, why do you need an AutoplaceControl? You can define the prototype and just place it with create_entity.

Proposal: add an optional size parameter to AutoplaceControl defaulting to true. When set to false, the "Size" slider in the map settings UI is removed (similar to how richness is optional).

Rationale: resources that are supposed to always spawn as a single node -- in that case would reduce user ...