Anyone over the age of 18 with a Working With Children Check can be a team mentor. Teachers and parents make ideal mentors and are well placed to facilitate the Australian STEM Video Game Challenge. A mentor can be shared by more than one team, meaning that a single teacher can exist as the mentor for multiple teams of students (i.e. a class).

The role of the Team Mentor is:

• To register their team(s) and the students within each team.
• To provide support and advice, encourage learning, and mediate any issues that might arise as their team’s progress through the game design process.
• To take responsibility for submitting the finished game and completed GDD (Game Design Document)
• Provide a reliable point of contact for communications between the Australian STEM Video Game Challenge and the participating students.

Team Mentors do not need to be experienced game designers or professionals in the IT area. The mentoring for most students will be in supporting their creative process, helping them to scale a design back to something they can manage in their available time and reminding them that simple ideas done well are generally the way to go.

A valid entry for the Challenge must include an original video game, a Game Design Document and a short screen recording of the key gameplay elements of the submitted video game.

Rules for the challenge

Submitted games MUST run in a Microsoft Windows operating system, or in an identified Internet browser.
• Games can be developed on any operating system. However, the final version of the submitted game MUST run on a Microsoft Windows operating system, or internet browser.

Submitted games MUST be built in free or free-for-education platforms.
• To ensure an equitable opportunity for all participants we insist upon the use of free or free-for-education platforms and prohibit the use of paid assets.

Judges MUST be able to see code.
• It is the Team Mentor's responsibility to ensure the correct files and/or links have been included in the submission. Note: Code is not visible for games made on platforms such as Roblox

Submitted games MUST utilise a keyboard and/or mouse-based control system and be playable for at least 5 minutes.

Submitted games MUST function, first and foremost, as single-player games.
To facilitate judging, we require that all games submitted in the Australian STEM Video Game Challenge are designed primarily for play by a single player.
• We do not discourage participants from submitting multiplayer games, however, we ask that these considerations be treated as secondary to the single player experience.

Submitted games MUST refrain from the use of store-bought or purchased assets.
• The development of characters, construction of environments and the realisation of artwork is an important component of the game development process, and part of the challenge that exists in creating an original game. At a minimum, we expect that the main characters and sounds, important tools and obstacles, as well as primary backgrounds are the student’s original work.
Please refer to our Official Rules for more details.

All entries must adhere to G rated classification guidelines. The classification guidelines can be found here.

To register your team please create a mentor account through our Mentor Portal in the menu bar at the top of this page.

Then register your team(s) during the registration period. Teams cannot be registered during the submission period, after team registrations close. See important dates for details.

All students must have parental permission. These are retained by the mentor. Parent permission form

Game Designer



Game Designers help to determine the rules and the structure of the game making sure that players can easily understand how to play the game. They need to think about the gameplay, the goals of the game, the balance of challenges and rewards, feedback to the player, levels and increasing difficulties. Game Designers need to be good communicators, helping to guide other members of the team.

Visual Designer

Visual Designers are responsible for the look and graphic design of the game, ensuring it is consistent throughout the game. Visual Designers are generally creative with an ability to visually represent concepts or ideas and take responsibility for the overall graphic style and appeal of a game.

Programmer

Programmers make the game work! They write the code, scripts and mechanisms that make the game functional and playable. Programmers are responsible for functionality and many of the technical aspects of game development.

Storyteller

Storytellers contribute to the narrative that underpins the game. They are responsible for providing the game with environments, characters, motivation and context. Storytellers are driven by player engagement - they think about what is happening in the game, how the story will progress through the game, and how the progression will help to encourage/challenge the player to continue playing.

Audio Designer

Sound and music can heighten the gameplay and bring the world of the game to life. Music can bring an emotional element to the game, while sound effects can add a dynamic atmosphere. Original sound and music can make a good game great!

Tester

The Tester is responsible for testing the game and ensuring that there are no glitches or technical problems. Tester’s play a valuable role in ensuring that games are functional, engaging and enjoyable. They provide insights on how the game feels to play, and the player experience.


(NB: It is recommended that you test your game with a person not connected to the build and design of the game – someone fresh will pick up problems that those who understand the game will not!).

Students may enter one of five categories
Year 3-6 Scratch
Year 3-6 Open Platform
Year 7-9 GODOT
Year 7-9 Open Platform
Year 10-12 Open Platform (First and second place acknowledged)

Open platform

There are many fantastic game platforms available for teaching and learning. We do not wish to limit participants to using just a few. You may submit an entry made in any free or free-for-education platform that suits your context, provided it satisfies the criteria outlined in the rules for the challenge. Remember that judges must be able to view the game code.

Scratch

Scratch was developed by the Lifelong Kindergarten at the Massachusetts Institute of Technology (MIT). Designed for beginners, Scratch utilises a ‘drag-and drop’ environment, and a simplified programming language to enable younger students program and share interactive media such as stories, games, and animation.
 Scratch (link)

GODOT

GODOT is a 2D and 3D cross-platform compatible game engine released as open source software under a license from MIT. GODOT aims to offer a fully integrated game development environment. Allowing young developers to create a game, needing no other tools beyond those used for content creation (art assets, music etc.). The website has great supporting information and tutorials for those new to GODOT and game development.
 GODOT Engine (link)

The Australian STEM Video Game Challenge judging panel is comprised of volunteers from the education, game development and technology sectors.

Each year games are judged in a three-round process. We have GDD templates and Scoring Rubrics specifically designed for each age group. Check out the age group tabs for more information.

Round 1: Qualifying (24-29 July, 2025)

This is a quality assurance round where judges check that games play, adhere to classification guidelines and that there is student content in the GDD. This is a great round to be a part of if you are new to the challenge or do not have a teaching or tech background.

QUALIFYING: Re-submission (1-6 August, 2025)

If we find an issue with a team’s entry during qualifying, we will notify the team’s mentor. Mentor's will have one opportunity to resubmit during the re-submission period. Any games that do not work after re-submission will not move on to the semi-finals.

Round 2: Semi-Finals (9-17 August, 2025)

In this round, judges receive a random selection of entries and use the challenge scoring rubrics to determine a score and provide written feedback to teams. Judges in this round require a sound knowledge of at least one of the category platforms. Ideally, judges will have experience using scoring rubrics and providing student feedback. If you are a digital technology teacher, this is your round!

Round 3: Finals (23 August-31 August, 2025)

This round is for experienced tech teachers and industry experts. Judges in this round receive a random selection of finalist games and use the challenge scoring rubrics to determine a score and provide written feedback to teams. Judging in this round requires in-depth knowledge of coding languages and extensive experience with gaming platforms. Teams that generate the highest score in this round are declared the winner.

You can register as a judge through the Judge Portal in the menu bar at the top of this page.