Skip to main content

Sieve

Binds a hopper as an item filter — only stacks matching its samples pass; the rest stay put. The last sample of each type stays locked so the filter cannot empty itself. Works with Vortex and freight.

Pattern​

Hover a tile to name it. Reading pattern diagrams explains the symbols.

3 × 3, one layer. Drawn flat on the ground, facing any compass direction.

ABABCBABA
  • Activation block
    The glowing cell is the one to click.
  • Spent
    Cells with a corner mark are used up when the rune wakes.

Keys

  • Redstone Dust × 4
    spent when the rune wakes
  • Piston × 4
    spent when the rune wakes
  • Hopper × 1
    stays after use

How it works​

The Sieve binds a hopper as an item filter. Wake it, and the pattern burns away while the hopper remains. Then place a sample of each item you want to let through inside the hopper.

From then on, only stacks that match a sample enter the hopper from the hoppers and containers feeding it. Everything else stays where it was. An empty Sieve lets everything through.

Good to know​

  • The last item of each sample always stays in the hopper, so the filter can never empty itself.
  • It works with a Vortex and with freight.
  • A hopper held by a Heavy Core Anchor refuses it.
  • Breaking the hopper ends the binding. The Sieve unravels with the hopper.

Tips​

Put a Sieve under a mob farm's collection chest to sort the drops you want from the rest.

Configuration​

These are the defaults in plugins/Runic/runes/sieve.yml. Every rune file also carries the shared settings described in Rune files.

Sieve has no settings of its own beyond the shared ones.

Messages​

8 messages this rune can show
KeyDefault text
boundThe Sieve awakens — place sample items in the hopper; only matches pass the line. Leave at least one of each sample — hoppers cannot pull the last.
already-boundThis Sieve already sorts the line — stock samples in the hopper.
conflict-heavy-coreA Heavy Core Anchor already claims this hopper — the Sieve will not bind.
limitThe server's Sieve safety limit has been reached.
consume-failedThe Sieve pattern could not be consumed safely.
transaction-failedThe Sieve binding failed; its pattern was restored.
registration-uncertainThe Sieve's state could not be verified; an administrator should inspect it.
brokenThe Sieve unravels with the hopper.