Who it's for
Intermediate and advanced for high school, and every level for college. It works as a two-day conference event or a semester unit, and it scales from a first-year programming class to a senior capstone.
HS intermediate–advancedCollege all levelsHead-to-head
Venture Bot · Robot Tanks
Plan the venture. Equip the tank. Win the arena.
Teams of three to five equip a virtual tank on a fixed budget, commit to a strategy, and pitch the whole plan to a panel of judges. Then their tank goes head-to-head against every other team's in a round-robin tournament. The original Venture Bot competition.
What students learn
Real skills, framed as a game.
Most students who take part have never done anything like it. They meet their team on Thursday evening and have a working, submitted tank by Friday night. Along the way they practice the things that matter long after the tournament ends.
- Reading a situation. Each turn the tank sees where things are and what it has left. Turning that into a decision, over and over, is the core of the game.
- Anticipating an opponent. Aim where the other tank will be, not where it is. Guess what the other team optimised for from the configuration they published.
- Defending a budget. Armor or speed. A bigger gun or more energy. Every upgrade has a cost, and the trade-off shows up in the arena and in the pitch.
- Explaining themselves. Judges score how clearly the team articulates what it decided, not whether they would have decided the same.
How a match plays
Two tanks, one arena. Teams write the instructions their tank follows on its own; nobody drives. The match ends when one tank is knocked out or the clock runs out, and running out the clock counts as a loss for both sides, so playing safe isn't an option.
What arena craft rewards
Winning isn't only about the last tank standing. Every round also scores how the match was played: using energy well, dealing more damage than you take, landing your shots, and ending matches decisively.
The Venture Bot process in this arena
Decide. Pitch. Compete. Reflect.
The four beats every Venture Bot team goes through, as they play out in the tank arena.
Decide
Who codes, who owns strategy, who owns the configuration, who presents. Then the budget: a web-based chooser lets the team spend a fixed amount on their tank, and what they skip matters as much as what they buy. Finally the language they'll build in and how they plan to win.
Pitch
Two to three-and-a-half minutes in front of a panel of professionals, hard cut-off. The team explains all four decisions and the reasoning behind them. Configuration choices are final and published to every team afterwards, so everyone knows what they're up against.
Compete
Code can keep improving right up to the submission deadline. Every team plays every team. Selected matches are screened on a big display for the whole event, and winners are announced at an awards ceremony.
Reflect
Every match can be replayed. Teams watch their plan meet another team's and see where it held and where it broke. That conversation, with a coach who asks "why?", is where most of the learning lands.
Scoring
The pitch is worth almost as much as the wins.
Judged presentationFive categories, 1–10 from every judge.
Match winsCumulative across all rounds.
Arena craftEfficiency, damage exchange, accuracy and decisiveness.
The venture angle
What a Tanks team has to defend
- Budget: which single purchase matters most to the strategy? If the budget were cut by a fifth, what goes first?
- Technology: why this language for this team? Who already knows it? What's the fallback if it stops working at 9 PM?
- Arena strategy: damage, efficiency, position or the clock? What does the tank do in the first ten seconds? What beats it?
- Team: who owns what, and who makes the final call when the team disagrees under pressure?
Run Robot Tanks
The original is ready for your students.
Two-day conference format or a semester unit. Pick an AI mode, and we'll handle the rest.