An example save file is attached (inserter_drop). To run it:
- There are two constant combinators towards the bottom. Momentarily enable the one on the left. This will cause the first train to move to the station, which will enable the inserter and load some items.
- After that train returns to its home, momentarily enable the combinator on the right. This will cause the second train to move to the station.
The inserter is only enabled for train A (train ID comparison). When train A arrives, the inserter does two drops of 6 items, filling a stack of 10 on the train and leaving 2 items in its hand. When train B arrives, the inserter remains disabled, but it still drops the 2 items into the train and returns home.
The expected behavior is for the inserter to do nothing when train B arrives.
Almost the same behavior is observed with unpowered inserters. See inserter_drop_power.zip. This example is used in the same way as the above except instead of enabling/disabling the inserter it turns its power on and off. This suffers from a similar issue: Even when unpowered, the inserter drops its contents into train B. The only difference here is the inserter does not return to home position when unpowered. The expected behavior, as with above, is for the inserter to do nothing when unpowered.
The test in both examples may be run again by just repeating the above process.
Note: Not interested in random neckbeards coming up with contrived justifications for why this makes sense or mansplaining why this happens: Imo, disabled / unpowered inserters should not take any actions, and it doesn't matter why they currently do.
