Bot Bash
Every real robot is a set of tradeoffs: more armor means more weight, and a bigger weapon means less power for everything else. Bot Bash makes students design inside those limits. It opens on a finished robot called Scout: a Raspberry Pi brain inside a PETG frame, two drive wheels and a drum spinner at the front, using 33 of the 150 weight allowed and 31 of the 50 power. Press Test to drive it with W A S D and spin the drum at a practice dummy. Then change one thing, add armor or swap the weapon, and test again to see what it cost.
Using this with a class? Make a free class and add your students yourself: each gets a username and password, with no email or Google account needed. Or give them one join code. Using Google Classroom? Post the link there; with a free class, the link also puts each student in your class, so you see their work. mytekDev is also available from the Google Workspace Marketplace, so your school's Google admin can install it for everyone.A first lesson: Everyone starts from Scout, adds four Armor Plates, and explains why the Speed number in Test fell from 0.34 to 0.23 while the Power bar did not move at all.
Set up a free class Share to Google ClassroomWhat a student actually does
They press Test and drive Scout around a small arena with W A S D. A practice dummy with 100 hit points waits in the top corner; they drive up to it and hold J, the drum spins, damage numbers float up, and the battery bar drains while the weapon runs. Then they go back to Edit and change something. Four Armor Plates on the sides add 16 weight, and in Test the Speed reading falls from 0.34 to 0.23. Swapping the drum for a Mega Blade costs 12 power instead of 6. Every change shows up in the Weight and Power bars before they ever test it.
From there they design their own. The grid is 16 by 16 and the parts are seven 3D-printing plastics (PLA, PETG, ABS, TPU, Nylon, Polycarbonate and CF PETG), a Raspberry Pi brain, an optional WiFi Module, drive and caster wheels, eight weapons and an Armor Plate. A robot has to have one Raspberry Pi that does not touch the edge of the grid, at least two drive wheels, every part connected to the Pi, and no more than 150 weight and 50 power; the Issues list says which rule is broken and floating parts are outlined. Templates loads five starting designs, Guide opens a table of every part's numbers, and the mirror buttons copy one side of a robot to the other. A saved robot goes into the Battle Arena, against one of five computer opponents in practice or against another student.
Scout with four Armor Plates added, in Test, holding J. The plates add 16 weight and no power, so Power stays at 31/50 while Speed drops from 0.34 to 0.23 and Turn from 0.72 to 0.49: the same two wheels now push a heavier robot. The battery falls while the drum spins and refills when it stops.
What they are learning while they play
Nothing here is presented as a lesson. This is what the activity is made of.
| What the student does | What it is |
|---|---|
| Watches the Weight and Power bars as each part goes on | Design constraints. A design has to meet fixed limits. Here it is 150 weight and 50 power, and every part spends some of one or both, so adding something means giving something else up. |
| Adds armor and sees Speed fall in Test | Mass and acceleration. The same push moves a heavier object more slowly. Each drive wheel gives the same push, so a heavier robot gets up to speed and turns more slowly. |
| Counts 15 for the Pi, 5 per wheel and 6 for the drum | Power budget. Every powered part draws from one supply. The brain and wheels take their share first, and what is left decides which weapon the robot can carry. |
| Holds J until the battery runs low | Energy use and recharge. A running weapon drains the battery faster than it refills. At zero the weapons shut off until the battery recovers to 20, though the wheels keep working. |
| Compares PLA, Polycarbonate and TPU in the Guide | Material properties. Materials differ in strength, weight and flexibility. A cell of Polycarbonate holds 24 hit points but weighs 2; PLA holds 10 and weighs 1; TPU is flexible and soaks up half the damage from a ram. |
| Moves a part and gets a floating-part warning | Structural connection. A machine only works if every part is attached to the rest. Each part has to connect back to the Raspberry Pi through neighboring cells. |
| Changes one part, then tests again | Iterative design. Engineers change one thing at a time and measure the result, so they know which change made the difference. |
How to tell whether it landed
Ask, and let them show you. A student who has understood it can answer these without help.
- Scout uses 31 of its 50 power. Which parts use it, and how much does each take?
- You added four Armor Plates. Why did the Power bar stay the same when the Weight bar went up?
- Why did Speed drop after the armor went on, when the wheels did not change?
- After the Pi and two wheels, how much power is left for weapons, and would a Mega Blade and a Flipper together fit?
- Your robot browns out halfway through a fight. Name two design changes that would help.
Use it in your subject
Not a technology class? Then the app is how students show what they learned in your unit. More projects for every subject.
Engineering and CTE
Design to a brief: the fastest robot that can still survive, or the most armor that still turns. Write down the tradeoff each part makes before placing it, then test whether it worked.
Physical science
Record Speed in Test for the same robot at four different weights by adding plates one at a time, and describe how speed changes as mass goes up.
Math
Plan a robot on paper first: add up its weight and power from the Guide table, check it against 150 and 50, then build it and compare the totals to the bars.
Practical notes
- AgesGrades 4 through 12. Younger students change a template and test it; older ones plan a design against the budget from the Guide's numbers and explain each tradeoff.
- TimeA minute to drive Scout in Test. Changing it and testing again takes ten minutes, and designing a robot from a blank grid most of a period.
- EquipmentA computer or Chromebook with a keyboard and mouse or trackpad, and a modern browser. Driving in Test uses W A S D and the weapons use J, K, L and the semicolon key, and removing a part is a right-click, so a touch-only tablet cannot do either. Nothing to install.
- CostFree. The app has no paid tier.
- PrepAbout five minutes: add the four Armor Plates to Scout yourself and compare Speed in Test before and after, so you know what the class will see.
- In a groupEveryone starts from the same robot and the same limits, so the class can compare designs by their numbers before any of them meet.
For co-ops, microschools, and classrooms
Give everyone the same budget and a goal, then let the designs meet. Every robot is built under the same 150 weight and 50 power, so a student who wins has to explain which tradeoff made the difference, and a student who loses can see exactly which numbers to change.
- Weight and power budgets that update as each part goes on.
- A test arena with a practice dummy before any real match.
- An in-app Guide with the numbers behind every part.
- No install, no per-seat license. Student work is private by default.
Common questions
Is it free?
Yes. It runs in your browser and there is no paid tier. A free account adds saving and the Battle Arena, but nothing on this page is behind a paywall.
Does it replace building a real robot?
No. It teaches the design side: working inside a weight limit and a power budget, and trading armor against speed. Real combat robot events also run by weight class, such as 1 pound antweights and 3 pound beetleweights. What it does not teach is the building. The parts are blocks on a grid, weight and power are game units rather than grams and watts, and there is no wiring, soldering or motor sizing. It works well as the planning step before a club or a kit build, or for students who have no access to one.
How does damage work?
Every part has hit points: its weight times the cells it covers times its material's strength, times 2. A PLA cell has 10 and an Armor Plate 224. In a match, each hit lands on a random part that is still attached, and a part with no hit points left breaks off. A robot loses when its Raspberry Pi is destroyed. If both survive 90 seconds, the one with the larger share of its hit points left wins. Flexible plastics soak up part of the damage from a ram, up to half for TPU, but not from weapons.
Does my child need an account to try it?
No. The demo on this page is the whole designer with Scout loaded, and Test works without signing in. Saving a robot and taking it into the Battle Arena need a free account.
How do the fights work?
The Battle Arena is a separate page that opens from the Battle Arena button. A student picks one of their saved robots and either practices against one of five computer opponents, joins a classmate with a six-character lobby code, or uses Quick Match. Practice matches give no rewards.
Does it run on a Chromebook?
Yes, with its keyboard. Driving and firing use keys, and removing a part is a right-click, which is a two-finger click on a Chromebook trackpad. A tablet without a keyboard cannot drive in Test.
Is a student's work public?
No. Robots are private by default. A student can choose to share one. In a class the teacher can see students' projects.
What subject can I log this as?
Most families log it as engineering: design constraints, materials and testing. The weight and speed comparisons count as physical science, and planning to a budget is math.
Still have a question? Ask us, and a person will write back.
Where to go next
Start with Bot Bash
Trying it costs nothing and takes about five minutes. An account is what makes the work last.
Bot Bash is one of the making apps on the platform. Every number on this page was read from the app itself with the Scout starter. It is a place to make things, not a course, and it is not a substitute for a teacher: it is at its best when an adult asks the questions above and takes the answers seriously.
Page last reviewed November 2026.
Google, Google Classroom and Chromebook are trademarks of Google LLC.