Thank you !

Hello !
Currently, SpoilToTriggerResult has a key "items_per_trigger" that allows us to define (if my understanding is correct) to trigger the script only if there is the required amount of items in the stack.

However, if we want to set this value to 1, meaning only one item is needed to trigger ...

Well it's true. "equipment" is an uncountable noun.
I learned something today.

Nice ! Thanks !

By the way, that raises another question : is it normal that the vanilla behavior is that, if you don't set the trash_inventory_size, it won't grow above 1 slot ?

Hello there !
It's me again, your friendly inventories bug finder :D

First, I thank you for fixing the trash inventory size setup for assembling machines : I tested it and it works fine.
However it seems to be broken for labs.

By default, the labs create a trash inventory when an item spoils ...

Hello,
When an item with a spoil to trigger result spoils while being inside a pod (tested with dropping a cargo pod from a platform), it looks like the event isn't fired.

I tested it with a breakpoint.
The event is fired when the item spoils while awaiting to be dropped by the platform (inside the ...

Hello !

Could you please add the defines : inventory.assembling_machine_trash ?
It looks like it's intended to be here, but currently missing.

I'm trying to hotswap items in several types of inventories with a script. It works for every inventory I have tried, except for assembling-machines.
I ...

That is indeed what I did, I was pretty sure I just tried putting a list of strings, but looking back at the code, I used the insert_item trigger with two items.

Still ! Have the ability to mod multiple results which could be mutually exclusive or not would be nice, in order to be able to spoil in ...

+1 to that
Currently, you can have multiple "spoil_result" for an item. Each spoil result can have a probability to happen.
But there is no way I'm aware of to make these results mutually exclusive.

Using the scripting option (spoil_to_trigger) can allow to make this possible, but runs into a wall ...

Hello there !
Unless I missed it, it looks like there is no setting for enabling a provider specific timeout. I disabled the global timeout for trains to make sure they will wait until they are empty before leaving a requester station.
But sometimes, my providers cannot load the requested amount of ...

Many thanks.

Hey ! Will you update this wonderful thing to 0.13 ?