Okay, I added an API to Item Request Proxy Events to register an item prototype so that if an item of that type spoils inside an entity, it'll fire an "item-spoiled" event (with the entity as part of the event data). This should obviously be used judiciously, but for e.g. modules spoiling in an ...

+1

BraveCaperCat wrote: Mon Jun 29, 2026 3:34 pm You're forgetting about when modules spoil, either into other modules or into regular items, which can change the module inventory.

Ah, you're right! I wonder if that's also possible to do automatically with script triggers and spoil_to_trigger_result?

Detecting when modules change can be done with the current modding API. Modules can only be changed by a player manually moving them, by item request proxies ("ghosts"), or by scripting.

For players manually placing/removing modules: a player can only change modules for an entity if it's their ...

It's not a perfect solution, but I made a mod, Tooltip Library, to handle a similar usecase. If used correctly, it has very minimal UPS cost.

I made a utility mod for item-request-proxy events: https://mods.factorio.com/mod/item-request-proxy-events

Okay, I just figured out that you can get events for item-request-proxy created by:

* Adding a created_effect with a "script" trigger item to the item-request-proxy prototype
* Subscribing to the on_script_trigger_effect event and filtering by effect_id

+1

This would especially useful for item-request-proxy entities created via the upgrade planner. There are only a few ways that an item-request-proxy can be created, and for most of them there are workarounds you can use (e.g. checking players' selected and opened ). But when an item-request-proxy ...

+1

I've encountered situations that would benefit from this as well, with entities and also recipes.

Uninstalling mods is probably the most common place where a feature like this would be useful. But it's also possible from changing mod startup settings, adding a mod, or anything that can change ...

+1, but...
I think there is a tradeoff here that's gone unnoticed: it would make it impossible to filter settings by any string that also happens to be a substring of any mod's name. E.g. if I search "alien" in the mod settings menu because I want to find settings called "alien X..." and "alien Y ...

Awesome, and thanks for that workaround!

Calling set_recipe() on an assembling machine LuaEntity , then writing (a non-zero value) to crafting_progress to it, causes the next craft to always be common quality, regardless of the recipe's actual quality. It's only for one craft, and the next one is always correct.

I've attached a scenario I ...

As I understand it, LuaEntity.previous_recipe is only used for setting the icon of a no-longer-crafting furnace, and it has no effect on any actual behavior of the entity. It would be a nice QoL feature for my mod (which can "hot-swap" a furnace with an assembling-machine version of it, and back) to ...

The documentation for defines.entity_status.waiting_for_space_in_destination says it's used by inserters and mining drills. However it's also used by recyclers (I believe it's used by any crafting machine with a non-nil vector_to_place_result).

Bumping this topic, just for the ability to hide entities in the upgrade planner GUI.

The original request was kind of a lot. Hopefully adding something 'hidden_in_upgrade_planner' is less of an ask .

+1

Add an event for when entities change due to a blueprint being pasted. This could be much larger than just changes in tags - also control behavior, modules, ...

You can use Blueprint manipulation library to achieve this. It has a function that maps blueprint entities to the entities they overlap ...

Thank you, this is great!!

As a sort-of followup to this request , it would be great to have the ability to exclude an ingredient from a recipe result's freshness. The motivation is to have a recipe with both a spoilable catalyst ingredient and a regular spoilable ingredient; the catalyst can't currently be returned ...

Another option would be to put the radius of generated chunks into utility constants, which would allow it to be changed in the data stage.