Item number only exists for complex item types. The event can be triggered by any type (basic iron plate with no data, thus no item number).


If the event were to pass item number, wouldn't it be fair to just pass nil for the basic items which don't have item numbers? As PennyJim said, that ...

item_number should be able to work just as well for my use case, if that would make more sense in general!

+1, I'd appreciate this to be able to create something akin to a custom deconstruction planner. The player could create multiple instances of a selection-tool, each with their own data/settings which can be edited via a custom GUI that's opened by on_mod_item_opened. I can manage the per-item data ...

Added LuaGuiElement::quality read/write for "sprite-button" type.

If this is what I think it is, THANK YOU! This was so annoying to implement with negative margins and such.

+1

Currently (2.0.11), SelectionToolPrototype allows a mod to specify SelectionModeData for each of the following modes:
select
alt_select
super_forced_select
reverse_select
alt_reverse_select

Each of the above has a corresponding on_player_*_selected_area event, except for super_forced_select ...

Ah, gotcha. That did the trick, thanks for the response!

According to https://wiki.factorio.com/Command_line_parameters , the command line argument "--fullscreen BOOL" should allow for toggling whether to start the game in windowed or fullscreen mode. I have attempted using both "--fullscreen false" and "--fullscreen true" (in separate attempts), both ...

Is it just me or should the names for the "stack inserter" and the "bulk inserter" be swapped now? Seeing as how one of them puts stacks of items onto belts, and it's not the stack inserter

For blueprints that are sufficiently tall, adding a LuaGuiElement anchored to the setup_blueprint GUI causes the green "Create blueprint" button to disappear. Also, the bottom portion of the GUI can be clicked through (you can interact with the taskbar even if the bottom of the setup_blueprint GUI ...