Skip to content

Merger occasionally allows items through a 0 marked input when it shouldn't #23

@tizubythefizo

Description

@tizubythefizo

Hi there,

So I've got a fully saturated mk1 line coming into the middle of a merger from a storage container, and another saturated mk 1 line coming into the "right" input slot (and nothing hooked up to the "left" slot).

I've got it set middle - 1 and take from right, right 0 and left at the default of "skip to next" (also tested "wait" on this, as well as "take from left" and "take from middle").

My understanding is, these settings should always prioritize input coming from the middle belt, and only ever allow something from the right to come through if there's empty space on the middle belt.

But that's not exactly what happens. Every few seconds it lets an item in from the right belt, which stops the middle belt (because the middle belt is fully saturated).

I'm assuming maybe it's a rounding error or something silly, but it's making the mergers work unreliably.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions