Understanding the FIRST LEGO League robot game missions
The robot game is the centrepiece of every FIRST LEGO League season, a high-energy 2.5-minute showdown where autonomous robots tackle themed missions on a purpose-built field. Teams across the globe, from Brisbane to Boston, spend months designing, building and programming their machines to maximise points through clever engineering and sharp strategy. The atmosphere at tournaments is electric, with crowds cheering as robots whir across the colourful mats and complete increasingly complex challenges.
For newcomers in Australia, understanding how the missions work is the difference between a robot that limps through a match and one that confidently clears half the board. This guide breaks down the field setup, the mission categories, the scoring rules and the programming approaches that successful teams use, with a few local tips for coaches and mentors along the way. Whether you are guiding a primary school squad in Perth or a high school team in Hobart, the principles remain the same, though the journey to a polished robot looks different for every group.
What the robot game involves
The robot game is one of three judging areas in FIRST LEGO League, sitting alongside the innovation project and core values. During a match, the robot operates completely autonomously for 2 minutes and 30 seconds, attempting as many missions as possible. Teams use LEGO Education SPIKE Prime, MINDSTORMS Robot Inventor or NXT kits to build their robots, programming them using block-based or text-based languages such as Python or Scratch-based environments.
Each annual challenge introduces a fresh set of around 12 to 15 missions on a themed field mat, bound by a wooden base. The field is consistent worldwide, meaning a team in Sydney uses the exact same setup as a team in Seattle or Singapore. Resources such as mdfirst.org provide official mission descriptions, field guides and rulebooks that Australian teams rely on for accurate setup and clarification of tricky rules.
A match begins with the robot in a designated launch area, and teams may touch the robot only when it is completely outside the home zone, with no parts touching home. This forces teams to design robust programs that can handle slight variations in launch position and field wear. Referees monitor the match closely, and any accidental interference with the robot or models can result in score reductions or penalties.
| Mission category | Typical objective | Example action |
|---|---|---|
| Manipulation | Move or reposition models | Pushing, lifting, pulling |
| Activation | Trigger a mechanism | Pressing a lever, turning a crank |
| Transport | Deliver an object to a target | Carrying, dropping, placing |
| Precision | Land on a specific marker | Balancing, stacking, aligning |
Reading the field and mission models
Every robot game field is a square mat surrounded by dual-lock compatible borders, with a collection of 3D mission models constructed from LEGO elements. The mat itself contains coloured zones, lines, and graphics that indicate where models sit and where robots can travel. Mission models are designed to be manipulated, triggered, or interacted with in specific ways described in the official mission documents, which include detailed photographs and scoring conditions.
Australian teams often practise in school halls or community centres, laying out the field on tables or the floor. It is important to ensure the mat is flat and the borders are securely attached, as even a few millimetres of warping can affect how the robot drives across the surface. Many clubs in Melbourne and Perth invest in portable table kits that meet the official dimensions, allowing them to host practice sessions or scrimmages. Lighting conditions also matter, as colour sensors can behave differently under fluorescent school lights compared to LED panels.
Key elements to study when reading a mission
- The required start state of the model before the match
- The expected end state for scoring
- Any constraints on how the robot may interact
- The number of points available and the difficulty curve
Building attachments and programming routines
Attachments are the tools a robot carries to interact with mission models. Common designs include simple pushers, hinged arms, scoops, and lifting forks. Sophisticated teams in Brisbane and Adelaide often use multi-function attachments that can be swapped quickly using a standardised connection system, reducing match downtime. Some advanced groups even experiment with cascading mechanisms that perform two actions in a single motion, saving precious seconds on the clock.
Programming routines require precise use of sensors, motor encoders, and timing. Gyro sensors help with straight-line driving and consistent turns, while colour sensors assist with line following and model alignment. Many Australian coaches introduce Python or block-based programming early, helping students transition to more advanced languages as their confidence grows. Debugging is a daily ritual during build season, with teams learning to trace problems through motor rotations, sensor thresholds, and attachment timing.
Programming considerations for reliable missions
- Use of sensor feedback rather than just timing
- Modular code structure for easy debugging
- Consistent base movement calibrations across different mats
- Simple, repeatable attachment operations
The same creative engineering mindset that drives a team to build a multi-purpose attachment also powers other hands-on pursuits. Some students channel this creativity into cultural and artistic projects, such as learning the intricate craft of Tibetan butter lamp making, where patience and precision are equally important. Both pursuits reward careful planning and an eye for detail.
Match strategy and scoring rules
Scoring in the robot game is based on the end state of models and the robot at the conclusion of the match. Most missions are worth between 5 and 30 points, with a few high-value targets offering bigger payoffs. Penalties exist for certain rule violations, such as interfering with another robot, touching the robot outside the designated intervention zone, or breaking a model. Understanding the scoring sheet is just as important as understanding the missions themselves.
Strategy involves deciding which missions to attempt and in what order. A common approach is to cluster missions by location on the field, minimising travel time and reducing the risk of getting stuck. Teams also weigh the reliability of a high-scoring mission against the consistency of easier ones, sometimes choosing to secure 10 reliable points over 30 risky ones. Many coaches in New South Wales and Victoria use heat maps to visualise which areas of the field their robot can reach consistently, helping to prioritise scoring opportunities.
During a match, teams may handle the robot only when it is completely outside home, and they may not touch any mission model directly. The head referee makes all final scoring decisions, and teams can request a score review immediately after the match if they believe a mistake has been made. Sportsmanship and gracious professionalism are core values that judges look for, even when a match does not go according to plan.
Practising effectively and competing in Australia
Consistent practice is the single biggest factor in robot game success. Australian teams typically meet two to four times per week during the build season, with at least one session dedicated to driving practice and another to programming refinement. Scrimmages between local teams help simulate tournament conditions and expose weaknesses in strategy or execution. Some community robotics hubs in Western Australia and South Australia host inter-school practice days, allowing teams to test their robots on official fields before qualifiers.
Competition pathways vary by state, with regional qualifiers feeding into state championships and, ultimately, the Australian FIRST LEGO League Championship. Major events are often hosted at universities or large venues, such as the Macquarie University campus in Sydney or the Melbourne Convention and Exhibition Centre. These events also feature project judging, core values activities, and robot design interviews, giving students a well-rounded STEM experience that extends well beyond the robot game mat.
Volunteers, mentors, and sponsors play a vital role in the Australian FIRST community. Many teams partner with local businesses or university engineering departments to access expertise and funding. Whether you are a parent, educator, or industry professional, there are many ways to support the next generation of Australian innovators as they tackle each season's robot game missions.
Coaches and team leaders are encouraged to register early for the upcoming season, download the official field setup guide, and connect with other Australian teams through online forums and social channels. Building a competitive robot takes time, but with the right preparation, your team will be ready to take on the missions with confidence and creativity. Visit the official resources, gather your kit, and start prototyping today, because the next great match is only a few build sessions away.
Maryland FIRST Robotics