What did you do?
Built this blueprint https://gist.github.com/stevetrov/7365f ... cbd3bba28a
to test something out.
What happened?
The stack inserter doesn't wait until it has a full stack before swinging.
What did you expect to happen instead? It might be obvious to you, but do it anyway!
I expected it to wait for a full stack of items and possibly get stuck.
Does it happen always, once, or sometimes?
This happens consistently. In previous versions the inserter would get stuck.
[2.0.23] Stack Inserters don't wait for a full hand when the set filter option is enabled.
Re: [2.0.23] Stack Inserters don't wait for a full hand when the set filter option is enabled.
The behavior had been changed to force a drop of the hand whenever the (changed) filter forbids the stack inserter from holding the item.
It would only be a bug if the inserter did drop it's hand even though the filter still permits it.
That used to be broken in a way that only enabling/disabling the inserter would cause re-evaluation of the filter. But dropping on filter mismatch was expected from the start.
It would only be a bug if the inserter did drop it's hand even though the filter still permits it.
That used to be broken in a way that only enabling/disabling the inserter would cause re-evaluation of the filter. But dropping on filter mismatch was expected from the start.
Re: [2.0.23] Stack Inserters don't wait for a full hand when the set filter option is enabled.
Not a bug. Decision was that when stack inserter holds items that are not allowed by the filters it is better to drop whatever it has rather than remaining in a stuck state.
Re: [2.0.23] Stack Inserters don't wait for a full hand when the set filter option is enabled.
Thats handy - so I can cancel the filter to force it to drop everything - like when changing recipes?