Follow the signal / Java Edition
Redstone Challenge
Components, signal strength, ticks, and circuit logic. Follow the signal and find the answer.
No questions are available for this mode. Choose another challenge.
Run complete
Your discoveries
Quiz rankings
Win streak
Longest correct-answer streak
No qualifying records yet. Set the first one.
Average speed
Correct answers · minimum 10
No qualifying records yet. Set the first one.
Most solved
Questions answered · right or wrong
No qualifying records yet. Set the first one.
Daily reset: 00:00 EST (UTC−5). Weekly reset: Monday 00:00 EST. Summer uses the same fixed UTC−5 clock. Rankings are separate for each quiz mode. Only your first answer to each question per EST day counts; weekly records include those daily answers. Speed uses server-measured time from opening a question to receiving its answer. An unanswered question abandoned for a new run breaks your current streak. Guests keep their Guest# number in this browser; signed-in records follow your account from a new run.
How to play & sources
Choose a mixed challenge or focus on component names, behavior, signal strength, ticks and delays, or practical circuit scenarios. Runs contain 10 or 20 different questions. A component can appear in more than one scenario. Correct answers earn one point; review the explanations after each answer and at the end.
Rules use Java Edition 26.3, normal 20 TPS, and no experimental redstone changes. One redstone tick equals two game ticks. Signal questions state all inputs and assume other sources are absent. Series delay questions add only the named repeaters.
Questions are checked against the collected Java catalogs and official Java implementations. Each explanation offers a further-reading link. View version, asset credits and rule provenance ↗. Component images use original Mojang / Minecraft textures, including static cube previews. Schematics illustrate the stated values; they are not an in-game circuit simulator.
No sign-in is needed. Personal bests stay in this browser. Question tiers and daily/weekly rankings use the shared quiz system below.
How question tiers work
Every question has its own community difficulty tier. The order below runs from easiest to hardest. This is the question’s difficulty, separate from your personal score.
- LT5
- MT5
- HT5
- LT4
- MT4
- HT4
- LT3
- MT3
- HT3
- LT2
- MT2
- HT2
- LT1
- MT1
- HT1
New questions start at HT5, marked provisional until five answers are counted. After every five counted answers, the tier moves by at most one step toward its community accuracy target. More correct answers move it toward LT5; fewer correct answers move it toward HT1. Two initial correct and two incorrect observations smooth small samples, so a few answers do not cause a sudden jump.
Only the first answer per question per browser per UTC day counts toward community statistics. Replaying still updates your score. An anonymous browser cookie keeps these daily counts separate; no sign-in is needed. Tier changes and counts are shared across players and saved on the server. If syncing is unavailable, you can keep playing, but the displayed tier may be outdated.
Build your redstone intuition
Start by identifying components, then follow how dust, repeaters and comparators change a signal. Work through delay chains and practical circuit questions to learn why a hopper locks, a piston stops, or a copper bulb remembers a pulse.
Read the circuit conditions
Redstone behavior can differ across editions and experimental settings. These questions use Java rules and explicitly distinguish game ticks from redstone ticks. Read both comparator side inputs and use the stronger one. Check the explanation after your answer to see the calculation.