Minecraft Redstone Basics: Repeaters, Comparators, and Your First Auto Door

What You Will Be Able to Build After This

By the time you finish this page you should be able to identify which component does the work in any machine you look at, diagnose your own failures precisely instead of saying "it broke", and build an automatic door from scratch on unfamiliar terrain.

The mental model that blocks most beginners is that redstone is electricity and dust is wire. That single misunderstanding is responsible for most "the game is buggy" complaints in the genre's most tinkered-with sandbox. People lay forty blocks of dust, see nothing happen at the far end, and assume the piston is broken, when what actually happened is arithmetic: the signal ran out of magnitude nineteen blocks ago.

Redstone is not a fluid flowing through copper. It is a small simulation running on two numbers you must hold in your head at all times.

The first is strength, an integer from 0 to 15. A lamp at the end of a long dust line fails because the number arriving is zero.

The second is time, measured in ticks. Every component resolves in a scheduled queue, and circuits that "work sometimes" usually do so because of timing, not luck.

Get those two ideas straight — strength counts down with distance, time counts up with every component you insert — and you stop copying designs and start writing them. That is the entire goal here.

The Three Mechanics Everything Else Is Built On

1. Strength is a number, and dust spends it

Redstone dust does not copy a signal; it inherits one and immediately spends a point. The rule is simple: a dust element takes the strongest source it can see among its neighbours, subtracts exactly 1, and publishes that as its own strength. If the strongest thing it sees is nothing, it publishes nothing.

The practical consequence is a hard range limit. A redstone torch, a lever, a block of redstone, a pressure plate with something standing on it, and the output side of a repeater all publish strength 15. Put dust next to any of those and the first dust reports 14, the second 13, and so on: fifteen powered dust, then zero. That is why long corridors need repeaters, and why you should place one every twelve or thirteen dust rather than fifteen — corners, vertical steps and stray inequalities eat into the budget, and you never want to discover the limit by watching a machine half-work.

A repeater does three jobs in one block, which is why it is the most important component a beginner learns. It refreshes the signal back to full strength 15. It acts as a diode, so power flows only the way its arrow points and cannot leak backwards into circuits that would otherwise chatter. And it deliberately delays the signal by one to four redstone ticks, which you set by right-clicking and watching the little piston-head arrow slide further back along its body.

2. Blocks carry power, but not equally

This is the rule that decides whether your machine can go through a wall, and the game never explains it.

A solid block adjacent to a redstone torch, a repeater output, a comparator output, or a block of redstone becomes strongly powered and pushes charge into dust on or beside it, so power can travel upward or sideways through solid matter.

Dust sitting on top of a plain block only weakly powers it: enough to run a piston, lamp or dispenser bolted to that block, not enough to light dust on the opposite face. That is why dust running over a block fails to reach dust beyond it.

When you need to inject deliberately through a block, point a repeater or comparator into it. Those components strongly power whatever they face, and suddenly the wall becomes a conductor.

3. Time is a queue, measured in ticks

The simulation runs on game ticks, twenty per second, so one game tick is 50 milliseconds. Redstone logic historically ran on a coarser unit, the redstone tick, which is two game ticks — 100 milliseconds. Repeaters are calibrated in redstone ticks, so right-clicking cycles delays of 0.1, 0.2, 0.3 and 0.4 seconds. A walking player covers roughly 4.3 blocks per second, meaning one redstone tick is about half a block of movement and a full four-tick delay is roughly two blocks. That conversion is how you eyeball door timing before building: if you have to clear three blocks of doorway before it shuts, you need a pulse comfortably longer than three ticks, so think about total pulse length rather than individual components.

Two more timings matter for everything you will build today. A redstone torch takes a tick to change state and inverts whatever it receives. Comparators also take one redstone tick and never refresh strength — they pass through whatever came in, which is precisely what makes them useful for reading containers.

Delay and behaviour reference

Comparators: Three Jobs in One Block

The comparator looks like a repeater with two tail torches, and that similarity is why beginners misread it. It is a tiny computer doing three unrelated things.

It reads. Point its back into a container and it publishes a strength based on how full that container is. The relationship is roughly this: take the total item count, divide it by the container's total capacity if it were packed with maxed-out stacks, multiply by fourteen, add one if there is anything at all, and round down. Empty publishes nothing. Anything non-empty publishes at least 1. Completely full publishes 15.

Ground it in numbers: a large chest holds 27 slots of 64 for 1,728 capacity, and one full stack works out to strength 1 — so you need several stacks before you even reach 2. Storage gauges built on comparators are blunt at the low end, which is exactly why item filters use five-slot hoppers instead of chests: less capacity means every single item moves the needle.

It compares. There are two inputs: the rear, marked by the single arrow, plus the sides. In compare mode it outputs the rear signal only if that signal is at least as strong as the strongest side signal, otherwise nothing.

It subtracts. Right-click so the front torch lights and the output becomes rear minus the strongest side input, floored at zero. Feed a constant into the side and you have raised the floor the main input must clear before anything comes out the front.

Both modes also make the comparator a diode, so it can never be back-powered, and both cost one redstone tick.

Component Reference You Will Keep Coming Back To

Walkthrough A: The Wall-Hidden Sticky Piston Door

This is the first door you should build, because every part of it is legible: when it fails, you can see why.

Goal: a one-wide, two-tall doorway that looks solid when idle and opens the moment you step on a plate.

Materials: 2 sticky pistons, building blocks, roughly 20 redstone dust, 1 repeater, 1 redstone torch, 1 stone pressure plate, two blocks matching your wall.

Step 1. Frame a doorway one block wide and two blocks tall. Change nothing else yet.

Step 2. On one side of the doorway carve two empty pockets into the wall, one level with the lower door position and one with the upper, each two cells deep. Count carefully: each pocket needs the cell immediately beside the doorway plus one cell further back, because that rear cell is where the piston body itself sits.

Step 3. Place a sticky piston in each rear cell facing toward the doorway, arm pointing across the gap. Put a block on each piston face. This matters: a sticky piston does not conjure a block. Without something stuck to its face it pushes nothing but air.

Step 4. Reason about polarity first, because this is the step everybody guesses. A sticky piston's resting state is retracted, so extended needs no power and retraction needs it. Your truth table: idle means doorway filled means extended and unpowered; triggered means doorway clear means retracted and powered. The plate must create power.

Step 5. Lay dust from the plate to both pistons. If the plate sits outside and the piston bodies sit inside a wall, bring the line up through a block adjacent to each piston using a repeater pointed into that block — never by running dust over one block and expecting the far face to conduct, per rule two.

Step 6. Test the resting state before touching the plate: both pistons extended, wall reading as continuous. Step on, both retract in the same tick. If only one moves, your line is reaching one pocket but not the other, and nine times out of ten the missing run crosses a block weakly.

Step 7. Set the repeater deliberately. A stone button gives about a second, a wooden button about a second and a half; a pressure plate gives exactly as long as you stand on it. If you sprint through and the doors clip your heels, add a repeater at two ticks on the line so the retract completes before you arrive.

If you want the door to stay open rather than open only while you stand there, this build is the wrong tool, and Walkthrough C is the right one.

Walkthrough B: The Comparator Item Filter That Sorts on the Second Item

Everybody wants a storage hall where cobblestone goes to one chest and diamonds to another, and the problem is always the same: one item has to trigger the sort, but the filter must never drain its own template.

The answer is a hopper whose slots are rigged on purpose.

Why 41-1-1-1-1 works. A hopper has five slots. Put 41 of your target item in slot 1 and exactly 1 of the same item in each remaining slot: 45 items out of a 320 capacity (five slots of 64). Because a partially filled slot will only accept more of the item already there, no unrelated item can ever enter this hopper — everything else flows straight past it. Only your target item can raise the count.

Now apply the container formula. Forty-five out of 320 is 0.1406, times 14 is 1.97, plus 1 is 2.97, rounded down to strength 2. One target item arrives, making forty-six: 46/320 is 0.1438, times 14 is 2.01, plus 1 is 3.01, rounded down to strength 3. That single-item jump from 2 to 3 is the whole trick, and it is why the template is 41-1-1-1-1 rather than 45 stacked in one slot.

The build sequence.

Step 1. Lay your transport line. Every hopper points into the next, ending at your sorting input or at overflow chests. Items travel at roughly one every eight game ticks — far faster than any survival input stream.

Step 2. Beneath each position where you want a pickup, drop a filter hopper pointing sideways into a collection chest. Each filter hopper is a branch hanging underneath the main line.

Step 3. Load the template: 41 of the target item in slot 1, 1 each in slots 2 through 5.

Step 4. Place a comparator with its back against the filter hopper, reading it, pointing away. Leave exactly two blocks of dust between that comparator's output and a solid block. Attach a redstone torch to that block so the torch delivers power to something adjacent to the filter hopper — a torch directly beneath it, or a strongly powered block beside it. Any power reaching a hopper locks it, and locked is our resting state.

Step 5. Trace the arithmetic and see how load-bearing every measurement is. At rest the comparator outputs 2; the first dust reports 1, the second reports 0, nothing reaches the block, so the torch stays lit and the hopper stays locked with its 45 items safe. A target item arrives, the comparator jumps to 3, the first dust reports 2, the second reports 1, the block gets power, the torch switches off, the hopper unlocks, and the surplus drains sideways into your chest. The count falls back to 45 and everything relocks. No clock, no input, no escape route for the template.

Why the two dust are not optional. Shorten the run to a single dust and resting strength 2 reaches the block as 1, so the torch never lights, the hopper never locks, and your template drains into storage within a minute. Every "my item filter ate my diamonds" story is this one measurement.

Scaling. Chain as many branches as you like along one line, keeping comparator runs from touching, and always terminate the line in an overflow chest so unknown junk has somewhere to go instead of jamming the first filter it cannot enter.

Walkthrough C: The Cross-Coupled Latch, for Doors That Stay Open

Pressure plates are fine for a doorway you walk straight through. They fail the moment you want persistence: a gate that stays open until you close it, a machine you want running while you mine, a farm you toggle from two locations. For that you need memory, and the simplest memory in the game is the RS NOR latch.

The idea. Cross-couple two gates so each feeds the other. Because each takes a tick to flip, the pair settles into whichever state you pushed it into and holds it. It is not a ring oscillator, because each side also takes an external input line that can overpower the feedback — that asymmetry is what makes it a latch rather than a clock.

The build sequence.

Step 1. Place two solid blocks a couple of cells apart, L and R. These are the input blocks.

Step 2. Attach a redstone torch to each. Each torch is one side's output and the inverse of whatever powers its own block.

Step 3. Cross-couple: dust from the L torch's output through a repeater into the R block, and dust from the R torch's output through a repeater into L. Those repeaters isolate each feedback path so neither side sees the other ambiguously, and they give each side a definite tick to settle.

Step 4. Add set and reset triggers. Run a button line into the L block through its own repeater, and another line into the R block. Dust takes the strongest source it can see, so each external input effectively ORs with the feedback arriving from the other side — that OR combined with the torch's inversion is what you need to build a real gate rather than two inverters arguing.

Step 5. Test like an engineer, not a gambler. Hit the L button once: L's block gets power, the L torch goes out, the feedback to R stops, R's torch lights, and R feeds back into L — keeping L powered after your button releases. The state flipped and it stays flipped.

Failure mode and fix. If it flickers instead of settling, you built a two-inverter ring oscillator: the feedback lines got crossed without their isolation repeaters, or a dust run is touching the opposite wire. Rebuild on flat ground with clear separation.

Wire the latch output into a T-junction feeding your door, put a second button on the far side, and you have a proper toggle gate: press once to open, walk through, press once to shut.

Advanced Applications Worth Knowing by Heart

Memory without latches: repeater locking. A repeater receiving power from its side locks into its current state and ignores further input until that side power stops. Point one into the side of another and you have a one-bit cell smaller and calmer than an RS latch — the basis of most counters.

Pulse extension with a fading container. Let a hopper feed a chest that a second hopper drains, with a comparator reading that chest. Output rises as items accumulate and decays as they drain — an adjustable timer built from inventory movement. Slower than a clock, far harder to break with stray timing.

Thresholding with subtract mode. Feed a constant reference into a comparator's side in subtract mode and it reports only what exceeds the reference. Chain two and you can express things like "open this overflow valve only above two thirds" with no moving parts.

Vertical wiring. A column of blocks with a torch on alternating faces carries power upward cheaply, and because each torch inverts, an even count gives correct polarity at the top while an odd count inverts it. Count them. Torch towers are also where Java's burnout rules bite, and Bedrock behaves differently here, so verify in your own edition.

Edge-case caution. Two tricks have been patched and unpatched repeatedly and deserve testing rather than trust: very short pulses sometimes used to move a piston out and back within one tick, and the Java-side behaviour known as quasi-connectivity, where a piston activates from power delivered to the position above it. Both are real, both are useful, neither should be load-bearing without a manual override.

The Mistakes That Waste Beginners' Evenings

Every failure below has a signature you can learn to recognise.

The too-long dust line presents as "it works when I stand near it", and the listener responds to nothing at all rather than weakly.

Expecting power to cross a wall looks random until you know the strong-versus-weak distinction: whatever is bolted to the block still works, while dust on the other side stays dark.

A backwards repeater is silent and gives no error. Because it is a diode it never pushes backwards, so always read the arrow before placing it.

A comparator in the wrong mode behaves sensibly most of the time and then blanks exactly when you need output: front torch lit means subtract, unlit means compare.

Using a torch as delay adds a tick but also inverts, which is how doors end up doing the opposite of what you intended.

Ignoring the push limit stops everything silently — roughly twelve blocks, and one immovable block in the train is fatal.

The burned-out torch clock in Java looks like a crash but is a protective rule: too many flips inside a few seconds and it takes a break.

An under-measured item filter drains its own template, because two will not decay to zero over one dust.

The rule covering all of them: when a machine fails, count something — strength, ticks, pushed blocks, torch flips. Redstone bugs are arithmetic you skipped.

A Two-Week Practice Plan With Self-Diagnosis

Days one and two: learn to read, not to build. Pick a machine you already own and trace it end to end, writing down for each dust run the strength at the source and how far it has left before zero. Self-diagnosis: if every answer is 15, you are assuming rather than counting.

Days three and four: Build A twice. Build it from the steps, then tear it down and rebuild from memory in different terrain — a hillside, a field, a one-thick wall. Self-diagnosis: if it works in one spot and not another, the difference is pocket placement or accidental power injection.

Days five and six: pulse length. Swap the trigger — lever, wooden button, stone button — and feel the difference between a second and a second and a half. That feeling lets you choose two-tick or four-tick repeaters later without guessing.

Second week: the filter, then deliberately broken. Build it for two item types, then wire it wrong on purpose — one dust too few — and watch the template drain. Push a single target item through and check that the comparator steps from 2 to 3. Anything else means your template is not exactly 45 items.

Then combine. Wire latch plus hidden door plus a status lamp so the machine reports its own state. When all three circuits live in one machine and you can explain every wire, you have graduated from copying to designing.

Where This Leaves You

Everything above reduces to two habits. Count strength, because distance is a resource you spend one point at a time. Count time, because every component you drop into a circuit is a promise about the order things happen in.

That is why some players watch a machine once and can describe it, while others rebuild the same door forty times: one knows redstone is arithmetic, the other waits for electricity to behave.