Simple Priority Merger issues
@Andre Aquila <Aquila Industrial> There are some issues with the Simple Priority Merger.
1. The hole being used for output is an input hole. The whole with the silver on top is where output should leave the merger. The hole opposite the current output hole.
2. It takes items from unprioritized input when it shouldn't sometimes. I think this may be a threading issues, like the order in which belts/mergers do factory tick. I tested this with 2 containers feeding the priority merger, outputting into a third container. I found that I was often able to trigger this incorrect behavior by opening the inventory of any of the containers. I think this may re-order when things get factory tick, leading to issue. Maybe we could look a little further down the correct input belt in case that hasn't had latest tick?
1. The hole being used for output is an input hole. The whole with the silver on top is where output should leave the merger. The hole opposite the current output hole.
2. It takes items from unprioritized input when it shouldn't sometimes. I think this may be a threading issues, like the order in which belts/mergers do factory tick. I tested this with 2 containers feeding the priority merger, outputting into a third container. I found that I was often able to trigger this incorrect behavior by opening the inventory of any of the containers. I think this may re-order when things get factory tick, leading to issue. Maybe we could look a little further down the correct input belt in case that hasn't had latest tick?
