No vanilla Minecraft crafter can see flower color. The crafter is a redstone-triggered 3x3 autocrafting block added in the Tricky Trials update (Java and Bedrock 1.21, June 2024), and every item that reaches its grid gets counted. The only way to route yellow flowers exclusively is to separate them before the crafter ever receives a signal, using either the item-form trick (yellow dye versus the other dyes) or a mod such as Create or Integrated Dynamics that reads color directly. A fully automatic flower farm feeding a vanilla crafter will fill with red, blue, and every other dye unless you build that filter stage first.
Why a Vanilla Crafter Cannot Read Flower Color
Start with the mechanism, because every workable design follows from it. The crafter holds nine slots and fires when a redstone signal hits it, pushing whatever recipe matches its grid. Nothing in that sequence checks what an item looks like or which flower produced it. Flower color lives in the item ID (minecraft:poppy versus minecraft:dandelion), and vanilla redstone components cannot query item IDs.
Hoppers, droppers, and minecarts with hoppers all move stacks by slot position and count, not by identity. That means an auto flower farm that dumps poppies, cornflowers, and oxeye daisies into the same chest will feed all of them into any crafter you attach. The crafter then crafts a mixed dye recipe and quietly consumes your yellow petals.
The fix is to convert the problem into one vanilla sorting already understands: item type. Yellow flowers become yellow dye at a crafting step or through a mod's processing, and dye colors are distinct items. Once that conversion happens, a standard item filter can gate the crafter input. The three viable routes are vanilla-only, modded with Create, and modded with a logic mod. I'll cover each with its actual limits.
Version matters here. Crafter behavior changed between the 1.21 release and the 1.21.2 through 1.21.4 patches, and Bedrock's redstone timing differs from Java's, so test on your exact version before scaling a farm. The flower-to-dye recipes themselves have been stable since dyes were introduced.
Mapping the Problem Before You Build: Farm Output and Crafter Input
Auto flower farms come in two shapes, and the shape decides how hard filtering is. A single-flower farm β one crop type planted on a grid β already produces only one dye color, so it needs no filter at all, just a crafter wired to a hopper line. A mixed farm, which most "auto flower farm" tutorials build because it saves space, outputs several species and needs real separation. Know which one you have before buying materials.
Write down the exact species list. In vanilla, yellow dye comes from dandelions and sunflowers, and only those two. Poppies, blue orchids, cornflowers, azure bluets, oxeye daisies, tulips, lilies of the valley, and wither roses all produce different dyes. Sunflowers are two blocks tall and need a different harvest mechanism than one-block flowers, which matters for farm layout.
The crafter side has its own constraint: nine slots. A yellow-dye block recipe needs nine yellow dye, which is fine, but if you're crafting something else, count the recipe's yellow-dye requirement. Any design that sends loose flowers into the grid wastes slots and can block recipes that don't match.
Budget the build. A single vanilla crafter costs one crafting table, two redstone dust, one dropper, and four iron ingots, according to the 1.21 recipe. Hoppers cost five iron each, and a comparator costs three stone plus one quartz. A four-species filter with comparators runs roughly 40 iron before you've automated anything, so plan the iron before the redstone.
Method One: Convert Yellow Flowers to Dye, Then Filter by Item
This is the only approach that works in unmodded survival, and it hinges on one fact: yellow dye is a single item. A hopper under a crafting setup that turns dandelions and sunflowers into dye produces a uniform output, and vanilla sorters can key on that item type. Nothing else in the flower set produces yellow dye.
The catch is that conversion must happen before sorting. If your farm harvests mixed flowers, run them through an autocrafting step that crafts each flower into its dye, then sort the dyes. That wider line needs one crafter per species or a manual conversion stage, which is why most players instead filter at the farm output.
For filtering, the standard vanilla design is a hopper line with comparator-gated sorters. Each sorter reads the filler items in its slots and passes only matching stacks onward, dumping mismatches into a side chest. Yellow dye passes to the crafter feed; every other dye falls away. This design is old and documented across the Minecraft community, and it works on 1.21 as long as you keep the filler items in place.
Failure handling matters more than the build. If the filter's filler items get pulled out by a stray hopper or a player, the sorter passes everything and the crafter fills with mixed dye. Put a chest with spare filler items next to the array and check it after every farm expansion. Also cap the crafter input with a hopper lock β a redstone-torched hopper β so a backup doesn't spill into the grid.
Method Two: Vanilla Item Sorters and Comparators Gating the Crafter
Here's the build in order, assuming single-flower output or a pre-converted dye line:
1: Place a hopper under the farm's collection chest so it feeds a horizontal hopper line. 2: Build a comparator sorter for yellow dye: a hopper with 41 filler items of one stack in slots 1β4, a comparator reading it, and a redstone repeater feeding the output hopper. 3: Repeat the sorter for each dye color you want diverted, feeding side chests. 4: Run the passing line into a hopper that feeds the crafter's top face. 5: Lock the crafter-feed hopper with a lever or torch so you can stop the line during maintenance. 6: Power the crafter with a redstone pulse from a button or a clock, not a constant signal, so it fires once per batch.
If the filter stops passing items, check comparator signal strength first β one wrong filler count drops the threshold and clogs the line. If the crafter fires with the wrong recipe, empty its grid and reload the recipe by hand before reconnecting redstone. If items back up into the farm chest, add an overflow chest with a second hopper line.
Signal strength is where most builds fail. The comparator output depends on how full the hopper is, and a hopper holding exactly 41 filler items of a non-stackable item behaves differently from 41 of a stackable one. Use stackable filler and count by stack, not item. This is the detail most tutorials skip.
Method Three: Create Mod Brass Funnels and Attribute Filters
If you're on a Create pack β Create remains one of the most-downloaded Minecraft mods and runs on 1.21 versions β the problem gets easier. Create's brass funnel accepts a filter, and the filter can be set to an item. Put a yellow dye or a yellow flower in the filter and the funnel passes only that item. No comparator math, no filler counts.
The Brass Funnel costs four brass sheets, one brass casing, and one electron tube in Create's recipe, per the mod's own recipe files. Build one per output line. The mod's filter system also honors attributes and tags if you enable them, but for flowers the plain item filter is the reliable choice. Create's item filter on a smart chute behaves similarly.
Create's edge case is the mechanical arm and frogport: if your farm routes through those, the filter position changes. Check the mod's in-game pondering scenes for the exact slot layout on your Create version, because filter UI moved between 0.5.1 and the later 6.x line. The key judgment is simple: filter at the funnel nearest the source, not at the crafter feed.
Create's own wiki and the in-game tooltips name the funnel as the filtering block, and the mod ships its own documentation. I'm not going to pretend I tested the exact 1.21 recipe count here; confirm the recipe in your pack's JEI. The design principle holds regardless.
There's a cost to Create too. Brass production needs a blaze burner, and the funnel chain needs rotational power. A simple vanilla sorter array is cheaper if iron is scarce and you don't already run Create. Choose Create if the pack already has it; choose vanilla if you're on a pure survival server.
Method Four: Integrated Dynamics or Logic Mods That Read Flower Type
Logic mods solve the problem at the deepest level because they can query item identity directly. Integrated Dynamics lets you write a variable card that tests an item against a list of acceptable IDs, then route matching items through a mechanical pipe. In that system, the filter is a logic expression, not a slot layout, so you can whitelist dandelion and sunflower and reject everything else.
The trade-off is setup time. Integrated Dynamics requires a logic programmer, variable cards, and an understanding of its variable system before the filter does anything. For a single farm, that's an hour of tutorial-watching. For a server with ten farms, it's the cheapest long-term option because one network can filter every line.
A simpler alternative is any mod with a tag-based filter, or a modpack's own item routing. Check your pack's quest book or JEI for a pipe or conduit that accepts item IDs. If it exists, wiring it is a ten-minute job and avoids both comparator math and Create's power requirement.
Test the expression before connecting the crafter: route output to a chest and watch one harvest cycle. If a mixed item appears, your ID list is incomplete or your pipe priority is wrong. Logic mods fail silently, which is worse than a comparator line that visibly clogs.
Method Five: Four Ways to Stop Mixed Flowers Reaching the Grid
Pick the gate that matches your build; each has a verdict.
| Gate method | Best for | Cost in materials | Main failure mode |
|---|---|---|---|
| Comparator sorter on yellow dye | Vanilla survival, converted dye line | About 5 iron plus redstone per sorter | Filler item drift changes signal strength |
| Create brass funnel with item filter | Create packs on 1.21 | Four brass sheets, one casing, one electron tube per funnel | Filter UI differs by Create version |
| Logic mod expression (Integrated Dynamics) | Servers with several farms | Logic programmer plus variable cards | ID list incomplete, fails without visible error |
| Hopper lock plus manual check | Tiny single-flower farms | One lever or torch | Human forgetfulness during farm changes |
The verdict splits on scale. One farm, vanilla only: comparator sorter. A Create pack: brass funnel. Five or more farms: a logic mod network. Any of the three beats a manual gate, which only exists to stop the worst spill.
Don't mix gates. A comparator sorter feeding a Create funnel doubles the failure points and makes fault-finding miserable. Pick one layer and put it closest to the source.
Wiring the Crafter Without Contamination
The crafter itself needs a clean feed even after filtering, and three details cause most contamination. First, the crafter pulls from the hopper above it only when a redstone pulse arrives; a constant signal makes it fire on every item. Second, the crafter's grid must hold a valid recipe or it drops items back out. Third, a comparator reading the crafter can gate the feed hopper so the grid never overfills.
Build the feed as hopper into crafter top, with a comparator on the crafter's side reading its contents and a repeater inverting that signal to lock the input hopper when full. This is the standard "crafter fullness lock" pattern documented in the Minecraft wiki's crafter article. It costs one comparator and one repeater and prevents the most common jam.
Then add the kill switch. A lever powering the feed hopper with a redstone torch lets you stop the line in one click. Use it before every farm expansion, and use it when you change the crafter recipe. Players who skip the switch end up with a chest of mixed dye they can't sort.
Pulse timing is the last trap. On Java 1.21, observers and redstone torches feed the crafter cleanly, but a torch clock can double-fire if the pulse is shorter than the craft time. Use a repeater to lengthen the pulse, and verify one craft per pulse before scaling.
Testing with a Mixed Harvest Before Scaling
Run one full harvest cycle through the system with the crafter disconnected. Open the output chest and count items. If any non-yellow dye or flower appears, the filter failed and you fix it before connecting the crafter. This single test catches nearly every design error.
Then connect the crafter and run three cycles. Check the crafter grid after each. A grid holding anything other than the intended recipe means the feed or the pulse timing is wrong. Log the count: expected yellow dye per cycle equals your farm's output rate, and any shortfall points to a sorter dropping items.
Scale only after both tests pass. Adding a second farm module before the first is verified multiplies errors. Build one module, prove it, copy it.
Keep a written note of the filler item counts, filter IDs, and pulse timings next to the machine. When a patch changes behavior, that note is the first thing you'll need.
Common Failure Cases and How They Present
Comparator drift. The line passes every color. Cause: filler items changed count, often because a hopper pulled one out. Fix: reload the filler stack and lock the sorter's input hopper.
Crafter firing empty. Nothing happens when the pulse arrives. Cause: no valid recipe in the grid. Fix: reload the recipe by hand and pulse once.
Mixed dye in the output. One non-yellow item reached the grid. Cause: sorter bypass or a hopper line that skipped the filter. Fix: trace the feed path backward from the crafter.
Farm backup. Flowers stack in the collection chest. Cause: the crafter's fullness lock never releases or the filter stops passing. Fix: check the comparator signal first, then the feed hopper lock.
Bedrock timing mismatch. Java designs don't fire on Bedrock. Cause: redstone update order differs. Fix: lengthen pulses with repeaters and test one cycle.
Matching the Method to Your Version and Pack
Java 1.21 and later carry the crafter, and the 1.21.2 through 1.21.4 patches didn't remove it. Bedrock added the crafter in the same update line, but redstone timing differs enough that Java sorter designs need retesting. The comparator sorter works on both; the pulse timing doesn't transfer.
Modded packs vary more. Create's 6.x line restructured some filter UI compared to 0.5.1, and packs pinning older Create versions need the older funnel workflow. Integrated Dynamics versions track Minecraft versions closely, so check your pack's mod list before assuming a machine works.
The version question is really a test question. Build one module on your exact version and pack, and treat every tutorial β including this article β as a starting point. The mechanics described here are stable, but the exact slot layouts and pulse lengths need your own test.
FAQ
Can the crafter itself be told to accept only yellow flowers?
No. The crafter added in 1.21 has no filter slot and checks only whether the grid matches a recipe, per the Minecraft wiki's crafter article. Every filtering approach must sit upstream in a hopper, funnel, or pipe. Players who expect a hidden filter menu waste time digging through the block's UI.
Do dandelions and sunflowers both make yellow dye?
Yes β those are the only two vanilla flowers that produce yellow dye, and both do so one flower to one dye. That's why a yellow-dye line can treat the two species identically after conversion. Every other vanilla flower yields a different dye color.
What is the cheapest single block that filters by item?
A hopper with a redstone-torched lock costs five iron and passes nothing while powered, which is a crude gate, not a filter. For real item filtering in vanilla you need a comparator sorter, roughly five iron and three redstone per color. Create's brass funnel is one block but costs brass, which needs a blaze burner.
Why does my sorter pass every dye after a while?
Filler items in the sorter hopper shifted count, usually because a hopper beneath pulled one out or a player grabbed one. The comparator signal strength then sits below the threshold and the sorter opens for everything. Reload the exact filler stack and lock the sorter's input hopper so nothing can pull from it.
Does this work on Bedrock Edition?
The comparator sorter does, but pulse timing needs retesting because Bedrock orders redstone updates differently from Java. Crafter designs that rely on observer pulses often need an extra repeater on Bedrock. Test one cycle before scaling either way.
Can I skip filtering by building a single-flower farm?
Yes. A dandelion-only or sunflower-only farm outputs one dye color, so no filter is needed β just a hopper line and a crafter. The space cost is higher than a mixed farm, and sunflowers need two-block harvesting, but the redstone cost drops to near zero.
What happens if mixed flowers reach the crafter grid?
The crafter tries to match a recipe; with mismatched items it finds none and holds the grid, blocking the feed line. Nothing is destroyed, but the farm backs up until you clear the grid by hand. That's the failure mode the filter exists to prevent.
Is there a datapack or command that filters the crafter?
Not in vanilla β the crafter's behavior isn't exposed to commands or datapacks for item filtering. Server operators sometimes use command blocks to clear a crafter's contents on a schedule, but that discards items rather than sorting them. Mods remain the only way to filter by flower type at the block level.