Over the next 10 labs you and a partner will work as a redstone engineering firm: learn how power, logic, timing and motion really work, then design, build, test and improve a working machine in a shared Minecraft world. Real circuits. Real bugs. Real Expo.
Minecraft Education is already installed. Join your teacher's hosted world using the picture-based Join Code from the Multiplayer tab on the Pause menu. Every pair gets its own plot, and it stays your plot for the whole project.
⚠ For teacher: download the class world file (City World .mcworld) and host it locally each lesson - students still join with the picture-based Join Code above, not this link.
⚡
Redstone Parts
Dust carries a signal about 15 blocks. A repeater restores it and adds a 1-4 tick delay. A torch flips a signal. Levers, buttons and pressure plates are inputs. Lamps and pistons are outputs. An observer gives a quick 1-tick pulse.
🎓
Skills Bootcamp
Labs 02 to 05 are hands-on mini challenges: power, logic, timing and motion. Stuck? Read Microsoft's Guide to Redstone or explore the free Redstone Museum world, six rooms that each explain redstone with a challenge.
⚠ For teacher: download the Redstone Museum world file (Redstone Basics .mcworld) and host it for the Lab 01 tour - students still join with the picture-based Join Code, not this link.
📋
Test Log & Tools
Engineers prove things with evidence. Keep a test log (paper or Canva) with results as numbers, like "worked 8 out of 10". Use the Minecraft Camera tool for progress screenshots and the Coordinates HUD to find your plot again.
🧠
AI Assistant
copilot.microsoft.com - ask it "How does a redstone X work in Minecraft Bedrock?" whenever you're stuck. Tell it you play the Bedrock-based Minecraft Education.
⚠ AI often describes the Java version of Minecraft, where some redstone rules differ. Always test what it says in your own world!
🏭
Expo Rules
On the final day every pair demonstrates its machine to visitors from the class, then a gallery walk lets everyone test the others. Reset your machine before every demo, and vote: Best Machine, Most Improved, Best Design and People's Choice.
// Logins & Submitting Your Work
🔑 Signing Into School & App Accounts
Need to log into Minecraft Education, Canva, or any other app that asks you to sign in? Most school and app accounts use the same login: your username is [email protected] (add a number if your name needs one, e.g. firstname.lastname2), and your password is the same one you use to log into your school computer.
📤 Submitting via Connect
Every project has at least one thing to hand in. Log into connect.det.wa.edu.au with your firstname.lastname and computer password, then head to your class and open the Submission section. Handing in more than one file? Zip them together first - total size must stay under 50MB.
// Primary Objective
With your partner, design, build, test and improve a working redstone machine that solves a client brief - then prove it works, with evidence, at the Engineering Expo.
Understand how power, logic, timing and motion work by building and testing small circuits
Design a machine on paper first, with a blueprint, a parts list and pass or fail tests
Test your machine again and again, and record real results in a test log
Improve your machine in a second version, using evidence instead of guesses
// Marking Key & Rubric
Criteria
Short Circuit (0-1)
Powered Up (2-3)
Fully Wired (4)
Master Engineer (5)
Score
Circuit Design
No blueprint, or the machine has no clear input, logic or output
Blueprint and parts list submitted, and the machine has an input and an output
Machine meets the spec: an input, logic or timing, an output, and it fits your plot
Design is neat and efficient, wiring is hidden or labelled, and choices are explained from the brief
/ 5
Working Machine
Machine does not work, or only works with teacher help
Machine works some of the time and does its main job
Machine works reliably and resets to its start state without rebuilding
Machine works every time for a stranger with no help, and includes a bonus feature
/ 5
Testing & Iteration
No test log, or Version 2 is the same as Version 1
Test log completed and at least one change made in Version 2
Test results clearly linked to three changes, and Version 2 shows each of them
Before and after results prove Version 2 is better, and remaining problems are honestly explained
/ 5
Expo & Communication
Did not demonstrate, or no build manual or reflection handed in
Demonstrated the machine and handed in a build manual and reflection
Clear demo using test evidence, specific feedback given to other pairs, and an easy-to-follow build manual
Confident demo that persuades with evidence, feedback acted on, and a polished manual and reflection
/ 5
Total
/ 20
Scroll sideways to see every column
Engineering Log
Week 1
01
🎯 Meet the Firm
▾
// LAB OBJECTIVEJoined the world and found your plot, firm name and roles chosen, top two briefs shortlisted, and 3 real machines researched.
Learn the challenge: in pairs you'll run a redstone engineering firm. You'll learn how redstone works, then design, build, test and improve one working machine for a client, and demonstrate it at the Engineering Expo
Launch Minecraft Education and join your teacher's hosted world using the picture-based Join Code. Find your pair's plot and stand on it - check your coordinates so you can always find your way home
Choose your firm name together. It goes on your build manual and on your machine at the Expo
Split the roles: one partner is the Builder (places blocks) and the other is the Tester (watches, records results and reads the guide). Swap every lab
Read the six client briefs below and choose your top two. Say what makes each one interesting and what might be hard about it. You'll lock in your final choice in Lab 06
Research: find 3 real machines or gadgets that do a similar job (a real automatic door, a lock, a traffic light, an alarm). Note what triggers each one and what it does
Tour the Redstone Museum world, a free Minecraft Education lesson with six rooms that explain how redstone works, each with a challenge. Your teacher will host it - join the same way as before, with the picture-based Join Code. Try each challenge and note which one taught you the most
🚪 Secret DoorClient: someone with a hidden base. Needs an entrance that looks like a plain wall when closed and opens and closes on command.
🔐 Combination LockClient: a vault owner. Needs a door that opens only when the right levers are switched on, and stays shut for any wrong combination.
🚦 Traffic Light ClockClient: a town planner. Needs lamps that cycle through a repeating pattern by themselves, with a way to switch it off.
🌾 Auto HarvesterClient: a busy farmer. Needs a farm that gathers its crop with no player breaking blocks by hand.
🚨 Alarm SystemClient: a museum guard. Needs something that detects a visitor crossing a line and triggers lights or sound, then resets.
🌉 DrawbridgeClient: a castle owner. Needs a bridge that extends across a gap when a lever is switched, and pulls back to close the gap.
💡 HintPick a brief where you can already imagine how the pieces connect: something goes in, something happens, something comes out. A simple machine that works every time beats a huge one that only works some of the time.
// ASK AI"Explain in simple terms what redstone is in Minecraft and what the difference is between an input and an output"
02
⚡ Power & Signals
▾
// LAB OBJECTIVEA working lever, dust and lamp circuit, your measured range recorded, and notes on how a lever, button and pressure plate each behave.
Set up a flat test bench in one corner of your plot. This is where all your small experiments go, so your main build area stays clear
Build your first circuit: a lever (input), a line of redstone dust (wire) and a redstone lamp (output). Flip the lever and watch the lamp
Range test: lengthen the dust line one block at a time until the lamp stops working. Microsoft's guide says a signal carries about 15 blocks - do you agree? Count and record your number
Put a repeater partway along the line to restore the signal, and see how much further it now carries
Swap the lever for a button, then a pressure plate. Write down how each one behaves: does it stay on, or only pulse on for a moment?
Start a diagram page in your test log: draw your circuit and label the input, wire and output
⚡ Signal Basics
Signal strength
Runs from 0 to 15. A power source starts at 15 and dust loses 1 per block
Range
Dust carries a signal about 15 blocks, then it fades out
Repeater
Restores the signal to full strength, so a long line works again
Redstone tick
Redstone runs at 10 ticks per second, so one tick is 0.1 seconds
💡 HintTest one thing at a time. If your lamp doesn't light, check the wire first: is there a gap, or is one block of dust missing? Most beginner circuits fail because of one loose link.
// ASK AI"In Minecraft Bedrock, how far does redstone dust carry a signal, and what does a repeater do to it?"
// LEVEL UPPredict how many repeaters you would need to carry a signal 45 blocks, then build it and test your prediction. Were you right? Write your numbers in your test log.
Week 2
03
🧠 Logic Lab
▾
// LAB OBJECTIVEWorking NOT, OR and AND gates, with a completed truth table for each one.
Learn what a logic gate is: a small circuit that decides its output from one or more inputs. Real computers are built from millions of them
Build a NOT gate with a redstone torch: a lever powers a block, and a torch on that block turns off when the block is powered. Flip the lever and record what the lamp does
Build an OR gate: two levers feeding one lamp, so the lamp lights if either lever is on
Build an AND gate: the lamp lights only when both levers are on. Research a layout with the image search or your AI Assistant, then build it
Test all four lever combinations (off-off, off-on, on-off, on-on) for your OR gate and your AND gate, and fill in a truth table for each
Stretch: explore the comparator. In subtract mode it takes the side signal away from the back signal, so a back signal of 10 and a side signal of 7 gives an output of 3
🧠 Gate Rules
NOT
Output is the opposite of the input. Input off gives output on, input on gives output off
OR
Output is on if any input is on
AND
Output is on only if every input is on
💡 HintStuck on the AND gate? Think about it backwards: an AND gate is the same as flipping both inputs with NOT gates, combining them with OR, then flipping the result with one more NOT.
// ASK AI"Explain the NOT, OR and AND logic gates using simple examples, then tell me how each one is built with redstone in Minecraft Bedrock"
04
⏱️ Timing & Clocks
▾
// LAB OBJECTIVEA working lamp chain, a clock with an off switch, and a recorded number of cycles in 30 seconds.
Learn that redstone takes time: every repeater adds a delay you can set to 1, 2, 3 or 4 ticks by toggling it, and 10 ticks make one second
Build a lamp chain: a lever feeding four repeaters in a row, each powering its own lamp, so the lamps light one after another. Change the delay settings and see how the pattern changes
Work out the timing: if you set every repeater to 4 ticks, how long is it between lamp 1 and lamp 4? Predict first, then test it
Try a short pulse: press a button and watch the signal. A pulse shorter than a repeater's delay gets stretched out to match the delay. Can you see it?
Build a clock: a loop of dust and repeaters that switches a lamp on and off again and again by itself. Research a layout with the image search or your AI Assistant
Add a way to switch your clock off. A machine you can't stop is a bug, not a feature
Time your clock: count how many on-off cycles it completes in 30 seconds, and record the number
⏱️ Timing Cheat Sheet
1 redstone tick
0.1 seconds
10 ticks
1 second
Repeater delay
1 to 4 ticks, so 0.1 to 0.4 seconds each. Chain them to make longer delays
Clock
A loop that feeds its own output back in, so the signal keeps turning on and off
💡 HintSlow is easier to debug. Set your repeaters to the longest delay first so you can actually see what each part is doing, then speed the clock up once it works.
// ASK AI"What is a redstone clock in Minecraft Bedrock and what is the simplest way to build one that I can switch off?"
// LEVEL UPChange the delay settings on the repeaters in your clock and count the on-off cycles in 30 seconds for at least three different settings. Which setting gives the fastest clock, and how do you know?
Week 3
05
🔧 Motion & Machines
▾
// LAB OBJECTIVEA working piston, sticky piston and observer, your push limit result recorded, and a list of circuits you could reuse in your final machine.
Learn the big idea: every machine, in Minecraft or in real life, does the same four jobs. Something starts it, something decides, something times it, and something moves or lights up. See the cards below
Build a piston that extends when you flip a lever and retracts when you flip it back
Swap it for a sticky piston and place a block on the end. Watch what happens when it retracts - a sticky piston can pull a block back
Push limit test: line up blocks in front of a piston and find out how many it can push. Microsoft's guide says 12 - test 11, 12 and 13 and record what really happens
Build an observer that watches a block and fires a lamp or piston when that block changes. Observers give out a quick 1-tick pulse
Combine two parts: a lever that runs a piston through a repeater delay. Can you make the piston move a second after the lever is switched?
Write down which of your circuits could become part of your final machine
1. InputWhat starts the machine: lever, button, pressure plate, tripwire or observer.
2. LogicWhat decides: torches, gates and comparators turn inputs into a yes or no.
3. TimingWhen it happens: repeaters and clocks control delay and repeats.
4. OutputWhat you see: lamps, pistons, sticky pistons, droppers and dispensers.
💡 HintPistons make a click you can hear, so listen. If a piston clicks but doesn't move, it's getting power but something is blocking it. If it doesn't click at all, the signal isn't arriving.
// ASK AI"What is the difference between a piston and a sticky piston in Minecraft Bedrock, and what does an observer do?"
// LEVEL UPChain two pistons so the second one moves about a second after the first, using a repeater delay to space them out. Draw a diagram of it in your test log.
06
📐 Blueprint & Spec
▾
// LAB OBJECTIVEA blueprint, parts list and 3 numbered tests that meet the Machine Spec, submitted.
Lock in your client brief from Lab 01. Write the client's need in one sentence: "My client needs a [machine] that [does what] when [trigger]"
Draw a blueprint on paper or in Canva: a top view and a side view of your machine, with the input, logic, timing and output parts labelled
Write your parts list: every redstone part you'll use and roughly how many of each
Write 3 tests your machine must pass, each with a number. For example: "the door opens 10 out of 10 times" or "the wrong combination fails 5 out of 5 times"
Check your design against the Machine Spec below. Does it meet every row?
Choose which mini circuits from Labs 02 to 05 you'll reuse, and which parts you still have to figure out
Export your blueprint, parts list and tests, and submit them through Connect
📏 Machine Spec
Input
At least one input the user controls, such as a lever, button or pressure plate
Logic or timing
At least one of: a torch, a gate, a comparator, a repeater delay or a clock
Output
At least one visible result, such as a piston moving, lamps lighting or a door opening
Reset
The machine must return to its start state without you rebuilding anything
Size
The whole machine must fit inside your plot
Safety
No TNT, and nothing that damages another pair's plot
💡 HintPlan to build the machine in small sections, and give each section its own test. A section that works on its own is a lot easier to fix than one hidden inside a huge circuit.
// ASK AI"Help me write 3 pass or fail tests, each with a number, for a redstone secret door in Minecraft"
📤 Submit via ConnectYour blueprint, parts list and 3 pass or fail tests (exported as a PDF or PNG)
Week 4
07
🏗️ Build Version 1
▾
// LAB OBJECTIVEVersion 1 built section by section, a screenshot build log started, and a first full test attempted with the results written down.
Open your blueprint and collect the parts on your list. Mark out the footprint of your machine on your plot before you place anything
Swap roles from last lab. The Builder places blocks, and the Tester checks every step against the blueprint
Build in sections: input first, then logic and timing, then output. After each section, test it on its own before joining it to the next one
Use signs or different coloured blocks to label your inputs, so anyone can tell what does what
Keep a build log: take a Camera tool screenshot after each finished section, with a one-line caption saying what it does
Run your first full test of the whole machine. It's fine if it doesn't work yet - write down exactly what happens instead
Check your reset works: after a full run, does the machine get back to its start state on its own?
💡 HintNever join two untested sections. If a joined circuit fails, you won't know which half is broken. Test each section alone, then join, then test again.
// ASK AI"What are good habits for building a big redstone circuit without getting lost or breaking it?"
📤 Submit via ConnectYour Version 1 build log (screenshots with captions, exported as a PDF or a zip of images)
// LEVEL UPAdd a status lamp to your machine that shows whether it is on or off, so anyone can tell its state at a glance. Test that it still works after a full reset.
08
🔬 Test & Debug
▾
// LAB OBJECTIVEEach test run 10 times with numbers recorded, one machine peer tested each way, and your top 3 changes written up as evidence, change and reason.
Run each of your 3 tests from Lab 06 10 times. Record how many times the machine passes each one, like "7 out of 10"
For every failure, write down what happened. Did nothing move? Did it move too late? Did it work once and then get stuck?
Debug like an engineer: trace the signal from the input, part by part, and find the exact place it stops or goes wrong. Test each section on its own if you have to
Peer test: swap machines with another pair. They try yours with no help from you, and you watch what confuses them. Then test theirs and give one specific piece of feedback
Rank your problems from most to least serious, then choose the top 3 to fix. For each one write the evidence, the change and the reason
Start on your first fix now, if there's time. Take a screenshot before you change anything, so you can undo it
📋 Evidence to Change Table
Evidence
What you saw or counted, with a number: "the door only opened 6 out of 10 times"
Change
What you'll alter: "add a repeater so the signal lasts long enough"
Reason
Why it should work: "the piston needs the signal for longer than the button gives"
💡 HintA bug you can repeat is a bug you can fix. If something fails only sometimes, keep testing until you can make it fail on purpose, then you'll see what's causing it.
// ASK AI"My redstone machine works sometimes but not every time. What are the most common causes of unreliable redstone circuits in Minecraft Bedrock?"
📤 Submit via ConnectYour test log with pass counts and your top 3 evidence-based changes
Week 5
09
♻️ Version 2 & Manual
▾
// LAB OBJECTIVEVersion 2 tested against Version 1 with real numbers, a finished build manual submitted, and a 60 second demo planned.
Make your top 3 changes from Lab 08, one at a time. After each one, write a short note: what you changed and why
Re-run the same 3 tests, 10 times each, and record the new pass counts next to the old ones in a before and after table. Did each change help? Use numbers, not opinions
Something still failing? Be honest about it. Write what you'd fix in a Version 3 and why - an honest result with a clear next step earns more than a hidden problem
Polish: hide wiring behind walls or floors, label the controls, and add lighting or signs so a visitor knows what to do
Create a one-page build manual in Canva: firm name, the client brief, a labelled screenshot or diagram, the parts list, how to use it, your before and after results and your next step
Export your build manual as a PDF or PNG and check that every number is readable
Plan a 60 second demo: the client's problem, how your machine solves it, one number from your tests, and what you improved
1. The ProblemWho is the client and what did they need? One sentence.
2. The MachineTrigger it live and show the input, the logic and the output.
3. The EvidenceShare one test number, like "10 out of 10 openings in Version 2".
4. The ImprovementSay what changed between Version 1 and 2, and why it worked.
💡 HintPut your best number in large text on the manual, like "10 out of 10 openings". One clear result is more convincing than a page full of small print.
// ASK AI"Give me a simple structure for a 60 second product demo that uses test results as evidence"
📤 Submit via ConnectYour build manual (exported as a PDF or PNG)
// LEVEL UPAdd a "Troubleshooting" box to your build manual: the 3 most likely faults a visitor could hit and how to fix each one. Base them on the failures you saw in Lab 08.
10
🏭 Engineering Expo
▾
// LAB OBJECTIVEDemonstrated your machine at the Expo, gave feedback to at least 2 other pairs, and submitted your manual, screenshot and reflection.
Join the world, go to your plot and reset your machine to its start state. Put a sign with your firm name next to it, and have your build manual ready to show
Safety and format briefing: visitors only touch a machine when its engineers say they can, nothing gets broken or rebuilt on another pair's plot, and everyone listens during every demo
Give your 60 second demo to visitors: the problem, your machine working live, one number from your tests and your improvement
Take part in the gallery walk: visit at least 3 other machines, try each one, and read their build manuals
Give one specific compliment and one specific suggestion to at least 2 other pairs. Base your suggestion on evidence you saw, not opinion
The class votes across categories: Best Machine, Most Improved, Best Design and People's Choice
Complete your final reflection: what went best, what you'd change with more time, and one thing you learned about logic, timing or testing
Submit your final build manual, screenshots and reflection through Connect
💡 HintIf your machine gets stuck live, don't panic. Reset it calmly and try again, then use it in your demo: "This is why we tested it 10 times" is a great thing to say.
// ASK AI"Help me write a short reflection paragraph about what I learned designing, building and testing a redstone machine in Minecraft"
📤 Submit via ConnectYour final build manual, a screenshot of your finished machine, and your final reflection
🏭
The Expo Awaits
After 10 labs of wiring, timing, testing and improving, your machine goes on show in front of the whole class. Every firm demonstrates, every firm tests the others, and the class votes for the awards.
SYSTEM ONLINE // YEAR 8 DIGITAL TECHNOLOGYREDSTONE ENGINEERS // 10 LABS
// Digital Technology - Year 8 //
REDSTONE ENGINEERS
10 labs. One working machine. You and a partner run a redstone engineering firm: learn how power, logic, timing and motion really work, then design, build, test and improve a machine for a client. Real circuits. Real bugs. Real Expo.
Use the arrow keys or the buttons below. Contents jumps to any lab.
// Contents
Pick a Lab
Review = that lab opens with a Daily Review (button in the lab's objective box on the page).
01
// Lab 01 · Week 1
🎯 Meet the Firm
// LAB OBJECTIVE
Joined the world and found your plot, firm name and roles chosen, top two briefs shortlisted, and 3 real machines researched.
// Lab 01 · The project
Your Firm, Your Machine
In pairs, you'll learn how redstone really works, then build one working machine for a client and prove it works with evidence at the Engineering Expo.
LearnPower, logic, timing, motionL02-05
BlueprintDesign on paper firstL06
BuildVersion 1, in sectionsL07
DebugTest 10 times, fixL08
ImproveVersion 2 + manualL09
ExpoDemo with evidenceL10
The roles
One partner is the Builder (places blocks), the other is the Tester (watches, records, reads the guide). Swap every lab.
Today
Join the world, find your plot and note its coordinates, pick a firm name, shortlist your top two briefs, and research 3 real machines that do a similar job.
// Lab 01 · Choose your client
Six Briefs
🚪 Secret Door
Looks like a plain wall when closed, opens and closes on command.
🔐 Combination Lock
Opens only on the right levers, stays shut for any wrong combination.
🚦 Traffic Light Clock
Lamps cycle through a pattern by themselves, with an off switch.
🌾 Auto Harvester
Gathers its crop with no player breaking blocks by hand.
🚨 Alarm System
Detects a visitor crossing a line, triggers lights or sound, resets.
🌉 Drawbridge
Extends across a gap on a lever, pulls back to close it.
Pick smartChoose a brief where you can already imagine it: something goes in, something decides, something comes out. Simple and reliable beats huge and flaky. You lock in your choice in Lab 06.
A working lever, dust and lamp circuit, your measured range recorded, and notes on how a lever, button and pressure plate each behave.
// Lab 02 · First circuit
Input ▸ Wire ▸ Output
Set up a flat test bench in one corner of your plot
Build it: a lever, a line of redstone dust, a redstone lamp
Range test: lengthen the dust one block at a time until the lamp dies. Record your number
Add a repeater partway along and see how much further it carries
Swap the lever for a button, then a pressure plate: how does each behave?
Debug habit #1Lamp won't light? Check the wire first: one missing block of dust is the usual culprit. Test one thing at a time.
// Lab 02 · The numbers
Signal Basics
Fact
Number
Signal strength
Starts at 15, dust loses 1 per block
Range
About 15 blocks, then it fades out
Repeater
Restores to full strength, adds a 1 to 4 tick delay
Redstone tick
0.1 seconds: redstone runs at 10 ticks per second
Inputs behave differently
Lever: stays on until flipped back
Button: a short pulse, then off
Pressure plate: on while something is standing on it
Which behaviour does your machine's brief need? Note it now.
Test log starts todayDraw your circuit and label input, wire and output. "The guide says 15 blocks": did your test agree?
03
// Lab 03 · Week 2 · Starts with a Daily Review
🧠 Logic Lab
// LAB OBJECTIVE
Working NOT, OR and AND gates, with a completed truth table for each one.
// Lab 03 · The big idea
Gates Decide
A logic gate is a small circuit that decides its output from its inputs. Real computers are built from millions of them. You're building three today.
🔄
NOT
Output is the opposite of the input. Built with a redstone torch: power the block, the torch turns off.
➕
OR
Output is on if any input is on. Two levers feeding one lamp.
✖️
AND
Output is on only if every input is on. The lock-builder's best friend.
Stuck on AND?Think backwards: AND is the same as flipping both inputs with NOT gates, combining with OR, then flipping the result with one more NOT.
// Lab 03 · Prove it
Truth Tables
Lever A
Lever B
AND lamp
OR lamp
off
off
off
off
off
on
off
on
on
off
off
on
on
on
on
on
Test all four
A gate isn't proven until you've tried every combination: off-off, off-on, on-off, on-on. Fill in a truth table for your OR and your AND.
⭐ Stretch: comparator
In subtract mode it takes the side signal away from the back signal: back 10, side 7, output 3.
04
// Lab 04 · Week 2
⏱️ Timing & Clocks
// LAB OBJECTIVE
A working lamp chain, a clock with an off switch, and a recorded number of cycles in 30 seconds.
// Lab 04 · Redstone takes time
Ticks & Delays
Timing fact
Number
1 redstone tick
0.1 seconds
10 ticks
1 second
Repeater delay
1 to 4 ticks (0.1 to 0.4s): toggle it to set
Longer delays
Chain repeaters: four 4-tick repeaters = 1.6s
Today's build: lamp chain
A lever feeding 4 repeaters in a row, each powering its own lamp, so they light one after another.
All four set to 4 ticks: how long from lamp 1 to lamp 4? Predict first, then test.
Pulse stretchingPress a button into a repeater: a pulse shorter than the repeater's delay gets stretched to match it. Watch for it.
// Lab 04 · Machines that run themselves
Build a Clock
What a clock is
A loop of dust and repeaters that feeds its own output back in, so the signal turns on and off forever: flashing lights, automatic farms, repeating patterns.
The golden rule
Add a way to switch it off. A machine you can't stop is a bug, not a feature.
Time it
Count the on-off cycles in 30 seconds and record the number: that's real test data for your log.
Debug habit #2Slow is easier to debug. Set repeaters to the longest delay first so you can see what each part does, then speed it up.
05
// Lab 05 · Week 3
🔧 Motion & Machines
// LAB OBJECTIVE
A working piston, sticky piston and observer, your push limit result recorded, and a list of circuits you could reuse in your final machine.
// Lab 05 · The pattern behind every machine
Four Jobs
Every machine, in Minecraft or real life, does the same four jobs. Your final machine needs all four, and you've now built three of them.
4. OutputWhat you see: lamps, pistons, droppers, dispensers
Spot the patternA real automatic door: sensor (input), "is someone there?" (logic), "stay open 3 seconds" (timing), motor (output). Name the four jobs in your client brief.
// Lab 05 · Make it move
Pistons & Observers
🟫
Piston
Extends when powered, retracts when not. Pushes blocks, but leaves them where they land.
🟩
Sticky piston
Same push, but it pulls the block back when it retracts. Doors and drawbridges live on these.
👁️
Observer
Watches the block in front of it and fires a quick 1-tick pulse when that block changes.
Push limit test
The guide says a piston pushes up to 12 blocks. Line up 11, 12 and 13 and record what really happens.
Debug habit #3Pistons click. A click with no movement means power arrived but something's blocking it. No click at all means the signal never arrived.
06
// Lab 06 · Week 3 · Starts with a Daily Review
📐 Blueprint & Spec
// LAB OBJECTIVE
A blueprint, parts list and 3 numbered tests that meet the Machine Spec, submitted.
// Lab 06 · The contract
The Machine Spec
Requirement
Rule
Input
At least one the user controls: lever, button or plate
Logic or timing
At least one of: torch, gate, comparator, repeater delay or clock
Output
At least one visible result: piston, lamps, a door opening
Reset
Returns to its start state without rebuilding anything
Size & safety
Fits inside your plot. No TNT, nothing that damages another plot
Lock in your brief: "My client needs a [machine] that [does what] when [trigger]."
// Lab 06 · Paper before blocks
Blueprint & 3 Tests
Draw a top view and a side view, with input, logic, timing and output labelled
Write the parts list: every part, roughly how many
Pick which Lab 02 to 05 circuits you'll reuse
Write 3 pass or fail tests, each with a number
Submit blueprint, parts list and tests via Connect
✗ Not a test
"The door works well."
✓ A test
"The door opens 10 out of 10 times." "A wrong combination fails 5 out of 5 times."
Plan in sectionsGive each section of the machine its own test. A section that works alone is easy to fix; one buried in a huge circuit isn't.
07
// Lab 07 · Week 4
🏗️ Build Version 1
// LAB OBJECTIVE
Version 1 built section by section, a screenshot build log started, and a first full test attempted with the results written down.
// Lab 07 · The build discipline
Build in Sections
Mark the machine's footprint on your plot first
Swap roles: Builder places, Tester checks each step against the blueprint
Build input ▸ logic and timing ▸ output, testing each section on its own before joining it
Label inputs with signs or coloured blocks so anyone can tell what does what
Run the first full test. Doesn't work yet? Fine: write down exactly what happens instead
Check the reset: after a full run, does it return to its start state?
Never join two untested sections
If a joined circuit fails, you won't know which half is broken. Test alone, join, test again.
// Lab 07 · Evidence as you go
Keep a Build Log
Camera tool
Screenshot each finished section with a one-line caption saying what it does. That's your build log, and it goes to Connect at the end of the lab.
⭐ Status lamp
Add a lamp that shows whether the machine is on or off at a glance, and check it still works after a full reset. Visitors at the Expo will thank you.
Use the Coordinates HUD to find your plot again, and keep the test bench circuits: they're spare parts for debugging next lab.
08
// Lab 08 · Week 4
🔬 Test & Debug
// LAB OBJECTIVE
Each test run 10 times with numbers recorded, one machine peer tested each way, and your top 3 changes written up as evidence, change and reason.
// Lab 08 · Numbers, not vibes
Run Each Test 10 Times
Test (from Lab 06)
Version 1 result
Door opens on command
6 / 10
Wrong code stays shut
5 / 5
Resets after a full run
8 / 10
For every failure
Write what actually happened. Nothing moved? Moved too late? Worked once then stuck? The shape of the failure points at the cause.
Repeatable = fixableIf it fails only sometimes, keep testing until you can make it fail on purpose. Then you'll see what's causing it.
// Lab 08 · Find the break
Trace the Signal
Start at the input and follow the signal part by part
Find the exact place it stops or goes wrong
Isolate: re-test that section on its own if you need to
Screenshot before you change anything, so you can undo
Peer test
Swap machines with another pair. They try yours with no help: watch what confuses them. Then write your top 3 changes as evidence ▸ change ▸ reason, like "opened 6/10 ▸ add a repeater ▸ the piston needs the signal longer than the button gives".
09
// Lab 09 · Week 5 · Starts with a Daily Review
♻️ Version 2 & Manual
// LAB OBJECTIVE
Version 2 tested against Version 1 with real numbers, a finished build manual submitted, and a 60 second demo planned.
// Lab 09 · Prove it improved
Before & After
One change at a time
Make your top 3 changes with a short note each. Then re-run the same 3 tests, 10 times each, and put the new pass counts next to the old ones. Did each change help? Numbers, not opinions.
Honesty scores
Still failing sometimes? Say so, and write what Version 3 would fix. An honest result with a next step earns more than a hidden problem.
Then polish: hide or label the wiring, label the controls, add lighting and signs so a stranger knows what to do.
// Lab 09 · Tell the story
Manual & 60-Second Demo
1. ProblemWho is the client, what did they need? One sentence.
2. MachineTrigger it live: input, logic, output.
3. EvidenceOne number: "10 out of 10 openings in Version 2."
4. ImprovementWhat changed from V1 to V2, and why it worked.
The build manual
One Canva page: firm name, brief, a labelled screenshot or diagram, parts list, how to use it, before and after results, next step. Best number in big text.
⭐ Troubleshooting box
The 3 most likely faults a visitor could hit and the fix for each, based on the real failures you saw in Lab 08.
10
// Lab 10 · Week 5
🏭 Engineering Expo
// LAB OBJECTIVE
Demonstrated your machine at the Expo, gave feedback to at least 2 other pairs, and submitted your manual, screenshot and reflection.
// Lab 10 · Open for visitors
Expo Day
Before your demo
Reset the machine to its start state
Firm-name sign next to it
Build manual ready to show
Demo: problem, machine live, one test number, improvement. 60 seconds.
Gallery walk
Visit at least 3 machines and try each one
One specific compliment and one specific suggestion to at least 2 pairs
Vote: Best Machine, Most Improved, Best Design, People's Choice
Expo rulesTouch a machine only when its engineers say you can, nothing gets broken or rebuilt on another pair's plot, and reset your machine before every demo.
// Lab 10 · Wrap up
Reflect & Submit
Reflection questions
What went best, and why?
What would you fix with more time?
One thing you learned about circuits, testing or debugging
The part the user controls to start a machine: lever, button or plate.
Choral Response
Signal strength
Redstone power runs 0 to 15 and dust loses 1 per block.
As tell BsBs tell As
Your circuit
Lever, then 20 blocks of redstone dust, then a lamp
What you expected
Flip the lever, lamp lights
Test bench - your plot
20 blocks of dust, no repeater
The lamp never lights. Why? How do you know?
As tell BsBs tell As
Your circuit
Lever, then 20 blocks of redstone dust, then a lamp
What you expected
Flip the lever, lamp lights
Test bench - your plot
20 blocks of dust, no repeater
Dust only carries a signal about 15 blocks. At 20 blocks it has faded to nothing. Add a repeater partway along: it restores the signal to full strength.
Multiple Choice
Which of these are true about redstone parts?
A lever stays on until flipped back
A button stays on forever
A pressure plate is on while stood on
Dust makes a signal stronger
A repeater restores a fading signal
A lamp is an input
Multiple Choice
Which of these are true about redstone parts?
A lever stays on until flipped back
A button stays on foreverA button gives a short pulse
A pressure plate is on while stood on
Dust makes a signal strongerDust loses 1 per block
A repeater restores a fading signal
A lamp is an inputA lamp is an output
4 Grid
Name the Part
Write the redstone part for each job
Start the machine by hand______________
Carry the signal along the ground______________
Restore a fading signal______________
Light up as the output______________
4 Grid
Name the Part
Write the redstone part for each job
Start the machine by handLever or button
Carry the signal along the groundRedstone dust
Restore a fading signalRepeater
Light up as the outputRedstone lamp
Match
Match each term to its meaning. Write your pairs, e.g. A - ?
Lever
A
W
Loses 1 strength per block
Button
B
X
Restores the signal, adds delay
Repeater
C
Y
Stays on until flipped back
Redstone dust
D
Z
A short pulse, then off
Match
Answer: A - Y B - Z C - X D - W
Lever
A
W
Loses 1 strength per block
Button
B
X
Restores the signal, adds delay
Repeater
C
Y
Stays on until flipped back
Redstone dust
D
Z
A short pulse, then off
Complete the missing components
In pairs, fill in A to F.
Item
Input, wire or output?
What does it do?
Learned in
Pressure plate
A.
B.
Lab 2
Redstone dust
C.
D.
Lab 2
Redstone lamp
E.
F.
Lab 2
Complete the missing components
In pairs, fill in A to F.
Item
Input, wire or output?
What does it do?
Learned in
Pressure plate
A. Input
B. On while something stands on it
Lab 2
Redstone dust
C. Wire
D. Carries the signal about 15 blocks
Lab 2
Redstone lamp
E. Output
F. Lights when the signal arrives
Lab 2
1 / 1
Year 8 Digital Technology Daily Review
Redstone Engineers: Logic, timing, motion
Choral Response
Logic gate
A small circuit that decides its output from its inputs.
Choral Response
Redstone tick
0.1 seconds. Redstone runs at 10 ticks per second.
As tell BsBs tell As
Your vault lock plan
Door must open ONLY when both levers are on
What you built
Two levers, each wired straight to the door circuit
Truth table - your test
your "AND" gate - test results
off + off ▸ lamp off
off + on ▸ lamp ON
on + off ▸ lamp ON
on + on ▸ lamp ON
The vault opens with just one lever. Why? How do you know?
As tell BsBs tell As
Your vault lock plan
Door must open ONLY when both levers are on
What you built
Two levers, each wired straight to the door circuit
Truth table - your test
your "AND" gate - test results
off + off ▸ lamp off
off + on ▸ lamp ON
on + off ▸ lamp ON
on + on ▸ lamp ON
That wiring is an OR gate, not an AND gate. Either lever alone powers the door. An AND gate lights only when every input is on: the off-on and on-off rows gave it away.
Multiple Choice
Which of these are true?
NOT flips its input
OR is on if any input is on
AND is on if any input is on
10 ticks is 1 second
A repeater delay is 1 to 4 ticks
A sticky piston leaves the block behind
Multiple Choice
Which of these are true?
NOT flips its input
OR is on if any input is on
AND is on if any input is onAND needs every input on
10 ticks is 1 second
A repeater delay is 1 to 4 ticks
A sticky piston leaves the block behindSticky pulls the block back
4 Grid
Timing Maths
Work out each answer
1 redstone tick______________
One repeater at max delay______________
Four repeaters at max delay______________
A clock is a loop that...______________
4 Grid
Timing Maths
Work out each answer
1 redstone tick0.1 seconds
One repeater at max delay0.4 seconds
Four repeaters at max delay1.6 seconds
A clock is a loop that...feeds its output back in
Match
Match each term to its meaning. Write your pairs, e.g. A - ?
The button's pulse is too short for the pistons. They click but only half-move: power arrives, then cuts out. Add a repeater to stretch the pulse, or use a lever. The failure shape points at the cause.
Multiple Choice
Which of these are good engineering habits?
Test each section on its own first
Join two untested sections
Run each test 10 times and count
Label inputs with signs
Screenshot before changing anything
Hide a failure from the manual
Multiple Choice
Which of these are good engineering habits?
Test each section on its own first
Join two untested sectionsYou won't know which half broke
Run each test 10 times and count
Label inputs with signs
Screenshot before changing anything
Hide a failure from the manualHonest results earn more
4 Grid
The Machine Spec
Write what the spec requires for each
At least one the user controls______________
A torch, gate, delay or clock______________
A visible result______________
Back to start, no rebuilding______________
4 Grid
The Machine Spec
Write what the spec requires for each
At least one the user controlsAn input
A torch, gate, delay or clockLogic or timing
A visible resultAn output
Back to start, no rebuildingA reset
Match
Match each term to its meaning. Write your pairs, e.g. A - ?