Home
// Digital Technology - Year 8 //

REDSTONE
ENGINEERS

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.

⚡ Redstone Circuits
🔧 Simple Machines
🧪 Test & Debug
🏭 Engineering Expo
Your Engineering Kit
🌍
The Workshop World
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.
// 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 strengthRuns from 0 to 15. A power source starts at 15 and dust loses 1 per block
RangeDust carries a signal about 15 blocks, then it fades out
RepeaterRestores the signal to full strength, so a long line works again
Redstone tickRedstone 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
NOTOutput is the opposite of the input. Input off gives output on, input on gives output off
OROutput is on if any input is on
ANDOutput 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 tick0.1 seconds
10 ticks1 second
Repeater delay1 to 4 ticks, so 0.1 to 0.4 seconds each. Chain them to make longer delays
ClockA 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
InputAt least one input the user controls, such as a lever, button or pressure plate
Logic or timingAt least one of: a torch, a gate, a comparator, a repeater delay or a clock
OutputAt least one visible result, such as a piston moving, lamps lighting or a door opening
ResetThe machine must return to its start state without you rebuilding anything
SizeThe whole machine must fit inside your plot
SafetyNo 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
EvidenceWhat you saw or counted, with a number: "the door only opened 6 out of 10 times"
ChangeWhat you'll alter: "add a repeater so the signal lasts long enough"
ReasonWhy 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.

⚡ Real circuits, tested
🗳️ Class-voted awards
🏆 Four titles to win

Find your partner and claim your plot // Lab 01

SYSTEM ONLINE // YEAR 8 DIGITAL TECHNOLOGY REDSTONE ENGINEERS // 10 LABS