How to automate iron blocks with a crafter in Minecraft

Compactor input, recipe and output

An original conceptual diagram, not a substitute for the video’s wiring. These batches assume iron-only input, nine enabled slots and a control that waits for a full recipe. The cited circuit is Java and has not been validated on Bedrock.

The visual reference

Duncan Geere’s illustrated Minecraft guide explains the crafter with in-game screenshots. Its examples help identify the block’s input and output. Here we prepare and check an iron application without attributing a circuit to an article that does not build it.

Prepare each stage of the automation

Separate supply, crafting and storage. For testing, use a dedicated iron input chest, its connection to the crafter and an output you can inspect. Then add the tutorial’s detector and control circuit. Keeping each stage visible distinguishes an ingot that never arrived from one waiting inside.

Mark the crafter’s output face before surrounding it with blocks. Leave access to its interface and wiring. Also provide somewhere to interrupt the supply: during testing, you should be able to stop input without dismantling the device or mixing the test batch with your base’s entire iron stock.

Prepare the chosen circuit’s materials as a separate list. A button works for the initial trial, but does not replace the detector or pulse control in the automatic version. First establish which condition activates the device and how it becomes ready for the next batch.

Three parts to check

A crafter crafts when it receives a redstone pulse and can accept ingredients through hoppers. A hopper directly underneath can extract ingredients: distinguish that position from the face that ejects the product.

Source: Duncan Geere — Crafting with the crafter

A first test with nine ingots

Prepare a crafter, nine ingots, a button and clear space to collect the output. This tests the recipe; it is not yet an automatic farm.

1. Keep all nine grid slots enabled.
2. Place one ingot in each slot and check the iron block recipe.
3. Press the button once and observe which face ejects the block.
4. Collect the result and repeat before connecting the farm’s production.

Why the comparator reading matters

The Java 1.21 release notes describe a crafter comparator signal from 0 to 9: each occupied or disabled slot adds one. Keep all nine slots enabled for iron blocks. A reading of nine then means nine occupied slots, although you must still check that they contain the correct ingredient.

Disabling slots can invalidate that interpretation. The detector does not itself verify that every item is an iron ingot. Test input filtering and the crafting condition separately instead of relying only on a lamp switching on.

After crafting, the control must be able to start another cycle. If the device works only once, observe its signal between batches: does it return to a waiting state or remain active? Triloms’ video provides the wiring; understanding the comparator reading helps you interpret what happens in that Java circuit.

Source: Minecraft Java 1.21 — Crafter

What the automatic circuit needs to solve

The input must supply only the intended ingredients and the control must wait for a complete recipe. A fast clock alone is insufficient: an early pulse can find a different or incomplete recipe.

Keep nine slots enabled for this recipe and test what happens when the iron runs out. Separate flowers or other items before the input. For the Java detector layout and wiring, follow the linked Triloms video. Its creator has not tested it on Bedrock; do not treat it as a validated build for that edition.

Test batches of 8, 9, 18 and 20 ingots

These are expected results for an iron-only compactor that waits for the complete recipe, not measurements of our build. Start each test with an empty crafter and transfer route. Count both output and remaining input; checking only the final chest can hide ingredients waiting in a hopper.

To test the detector, avoid inserting everything at once. Add ingredients gradually and watch when it triggers, then repeat with a continuous batch. Together, these checks can expose a system that works with a hand-filled recipe but fires too early when ingredients arrive individually.

1. 8 ingots: no block should be produced yet; ingredients should remain in the system.
2. 9 ingots: one iron block, with no remaining ingots once the cycle finishes.
3. 18 ingots: two blocks after both crafting cycles.
4. 20 ingots: two blocks and two ingots waiting inside the system.
5. Interrupted supply: stop before reaching nine ingredients and check that operation resumes correctly when input returns.

Before connecting your main storage

Try small batches and inspect both the output and the remaining contents. Then try interrupting the supply and filling the output chest.

If it only crafts once, check whether new pulses arrive. If ingredients disappear, inspect their route. Keep the crafter accessible: decorating can wait until these checks are resolved.

What to check before leaving it running

Temporarily fill the output container in a copy of the world and watch where the next product ends up. Do not assume the whole chain stops automatically. The design needs an overflow response: reserve storage, a supply stop or a warning that lets you intervene before items are lost.

If unexpected products appear, stop supply and inspect the grid before emptying it. Save a picture showing its contents, enabled slots and when the pulse arrives. If ingots seem missing without visible output, inspect every container along the route before blaming the crafter.

Finally, restore normal supply and repeat a small trial. Label input and output so another player does not insert unrelated materials by mistake. Keep access to the slots and control circuit; compacting saves space, but does not remove the need to inspect storage.