# Game Dev Academy Unity courses for kids aged 10 to 16. Online or in person in Melbourne. Beginner, Intermediate and Advanced. Part time, 2 hours a week for 6 months. ABN 84 612 409 773. study@gamedevacademy.com.au. +61450210940. Melbourne, Australia. Game Dev Academy is not a registered training organisation. Fees include GST in AUD. ## How you study Choose Online or In person. Hours, fees and coursework match for both. Online classes are live on video, Melbourne time. In person classes are in Melbourne. We confirm the class time and venue when we offer a place. ## Tutor Game Dev Academy is taught by Dinuka Jay, a senior Unity software engineer in Melbourne. 10 years of professional Unity development and 20 years of C#. Games, 3D applications and museum work released to more than 1 million users. His recent work includes leading Unity development for Triceratops: Fate of the Dinosaurs at Melbourne Museum, an exhibition featuring Horridus, the most complete Triceratops fossil in Australia. Other projects include AR applications, mobile games and 3D experiences for government, studios and independent teams. ## Games, AR and 3D Unity projects developed by the tutor. Students learn Unity in the editor used to build these projects. ### Chin Kaw's Shop AR mobile app. An augmented reality app about Chinese-Australian heritage. Place a herbal cabinet in the room and open drawers to find artefacts. ### Grandpa Jack Mobile game. A cartoon tower defence game. Players protect a garden from waves of critters. ### Bearcrest 3D experience. A real-time 3D world in Unity, with environments, interaction, and visual storytelling. ## Fees Prices include GST. Choose per session, monthly or in full on the apply form. Each option is a payment plan for the full 6 month fee. After the 14 day window before the first class, the full fee remains payable if a student leaves. Australian Consumer Law still applies. Read the refund policy before you pay. ### Beginner Game Dev Course Ages 10 to 12. $180 per session, $720 a month, $4320 in full. ### Intermediate Game Dev Course Ages 12 to 14. $200 per session, $800 a month, $4800 in full. ### Advanced Game Dev Course Ages 14 to 16. $250 per session, $1000 a month, $6000 in full. ## Courses # Beginner Game Dev Course Ages 10 to 12. For students who are new to Unity and to making games. Students who are new to Unity learn to design, code and finish a playable game. One 2-hour class a week for 6 months, online or in person in Melbourne. GST included: $180 per session, $720 a month, $4320 in full. Online or in person in Melbourne, 2 hours a week for 6 months. ## What you finish with By the end of the course, the student will have designed, programmed, built and published their own playable 3D game. - A playable original 3D game exported to run at home - A zombie survival mini-game, a space shooter, and a small RPG along the way - Unity editor, scenes, GameObjects, physics, UI, audio and builds - C# variables, conditions, functions, loops, lists and simple classes - No 2D art or 3D modelling required. The course uses pre-made Unity assets ## Week by week ### Month 1: Unity Fundamentals The editor, GameObjects and a character that moves. #### Week 1: Welcome to Game Development - What is a game engine? - How games are made - Introduction to Unity - Unity Editor tour - Scenes and GameObjects - Play Mode - Creating the first scene - Using pre-made 3D assets Mini project: Explore a simple 3D environment. #### Week 2: GameObjects and Components - Transform - Position, rotation and scale - Components - Rigidbody - Colliders - Prefabs - Organising a Unity project Mini project: Build an interactive obstacle course. #### Week 3: Player Movement - Introduction to C# - Scripts - Variables - Update() - Keyboard input - Player movement - Rigidbody physics - Camera following the player Mini project: Create a controllable 3D character. #### Week 4: Interactions - Collision detection - Triggers - OnCollisionEnter - OnTriggerEnter - Tags - Destroying objects - Simple interactions Mini project: Collect coins and reach an exit. ### Month 2: Learning to Code Through Games C# used on the thing the student is already making. #### Week 5: C# Fundamentals - Variables - Integers - Floats - Strings - Booleans - Operators - Debug.Log() Mini project: Create a simple game scoring system. #### Week 6: Decisions and Game Logic - If statements - Else statements - Comparison operators - Boolean logic - Game states Mini project: Create locked doors and keys. #### Week 7: Functions - What functions are - Creating functions - Parameters - Return values - Reusing code - Organising scripts Mini project: Build a reusable interaction system. #### Week 8: Loops and Collections - For loops - While loops - Arrays - Lists - Iterating through objects Mini project: Create a collectible system. ### Month 3: Game Mechanics A zombie survival game: health, enemies, weapons and a game loop. #### Week 9: Health and Damage - Health systems - Taking damage - Healing - Death - Respawning - Health UI Project feature: Player health system. #### Week 10: Enemies - Enemy GameObjects - Basic enemy AI - Following the player - Attack distance - Enemy health - Enemy death Project feature: Zombies chase the player. #### Week 11: Weapons - Shooting - Raycasts - Projectile basics - Damage systems - Ammo - Reloading Project feature: Player can fight zombies. #### Week 12: Game Loop - Score - Waves - Enemy spawning - Timers - Game Over - Restarting the game Project feature: Complete mini zombie survival game. ### Month 4: Making a Complete Game A space shooter with UI, menus, audio and difficulty. #### Week 13: Game UI - Canvas - Text - Buttons - Images - Health bars - Score displays - UI updates through code Project feature: Complete game HUD. #### Week 14: Menus and Game States - Main menu - Pause menu - Game Over screen - Restart button - Scene loading - Game states Project feature: A full game flow: menu, play, pause, game over. #### Week 15: Audio and Feedback - Sound effects - Background music - Audio sources - Particle systems - Screen shake - Visual feedback Project feature: Make the game feel responsive. #### Week 16: Spawning and Difficulty - Enemy spawning - Randomisation - Difficulty progression - Enemy waves - Power-ups - Balancing Project feature: Complete arcade-style space shooter. ### Month 5: Building an RPG NPCs, quests, inventory and saving across scenes. #### Week 17: NPCs and Dialogue - NPC interactions - Dialogue systems - Dialogue UI - Conversation states - Simple branching dialogue Project feature: Talk to NPCs. #### Week 18: Quests - Quest objectives - Quest states - Completing objectives - Rewards - Quest UI Project feature: Complete a simple quest. #### Week 19: Inventory and Items - Items - Inventory system - Picking up items - Using items - Currency - Shops Project feature: Functional inventory and shop. #### Week 20: Multiple Scenes and Saving - Scene management - Scene transitions - Persistent data - Save system - Load system Project feature: Play across multiple areas and save progress. ### Month 6: Build Your Own Game The student designs, prototypes, polishes and exports an original 3D game. #### Week 21: Game Design - Choosing a game idea - Core gameplay loop - Game mechanics - Player goals - Win and lose conditions - Creating a simple game design document Deliverable: Game concept and development plan. #### Week 22: Prototype - Build the core mechanic - Player controls - Basic gameplay loop - Test and iterate - Identify problems Deliverable: Playable prototype. #### Week 23: Development and Polish - Complete gameplay systems - UI - Audio - Effects - Difficulty - Bug fixing - Playtesting Deliverable: Feature-complete game. #### Week 24: Release - Final testing - Bug fixing - Performance basics - Creating a game build - Exporting the game - Creating a game icon - Final presentation Deliverable: A playable original game you can show to friends and family. ## What you need Online classes need this setup at home. In person classes are in Melbourne. Students still need a computer at home for homework. - A computer that can run a current Unity LTS release - Unity Personal, which is free - A reliable internet connection for live video - A microphone so the student can ask questions - Headphones if the house is noisy - Students under 16 join from a shared family space ## Is this for someone who has never opened Unity? Yes. Beginner assumes no Unity and no C#. Ages 10 to 12, or an older student who is new to Unity. ## Is it 2D or 3D? 3D, using pre-made assets. Class time is spent on programming, mechanics and finishing games. ## What do they finish with? A playable original game they can export and show, plus smaller games built during the months. https://www.gamedevacademy.com.au/courses/beginner # Intermediate Game Dev Course Ages 12 to 14. For students who have finished Beginner, or equivalent. Students plan a small 2D or 3D project, work in weekly builds, and practise animation, UI, audio and a final export. GST included: $200 per session, $800 a month, $4800 in full. Online or in person in Melbourne, 2 hours a week for 6 months. ## What you finish with A small 2D or 3D game taken through weekly builds to a playable export for Windows or Mac. - A working method: plan, weekly build, cut, polish, export - A playable 2D or 3D project with UI, audio and animation - A Windows or Mac build someone else can run - Playtest notes and a playable project ## Week by week ### Month 1: Scope and a production plan Pick a small 2D or 3D game you can finish, then break it into weekly builds. #### Week 1: What you will ship - Review of Unity production habits - 2D vs 3D for a six-month scope - Reference games - A one-page design Deliverable: A one-page game plan the tutor signs off. #### Week 2: Project setup - Folders and naming - Scene structure - Version habits - A vertical slice target Deliverable: A clean project with a playable empty scene. #### Week 3: Core loop first - The smallest fun loop - Player action - Feedback - Fail and retry Weekly build: A loop you can play in under a minute. #### Week 4: Build 1 review - Playtest notes - Cut vs keep - Risk list - Month 2 plan Weekly build: Build 1 tagged and notes written. ### Month 2: Player, camera and world Controls and a camera stable enough to build on for the rest of the course. #### Week 5: Player controller - Input - Movement feel - Grounding - Animation hooks Weekly build: A controller you would show a parent. #### Week 6: Camera - Follow camera - Damping - Bounds - 2D vs 3D camera choices Weekly build: A camera that follows the player cleanly. #### Week 7: Level blockout - Greybox spaces - Checkpoints - Pacing - Kill volume and resets Weekly build: One complete space that plays start to finish. #### Week 8: Build 2 review - Playtest with a classmate - Bug list - Scope cut if needed Weekly build: Build 2 with a written bug list. ### Month 3: Systems that carry the game Health, scoring, spawning or inventory, whichever the project actually needs. #### Week 9: The main system - One system, done properly - Data vs view - Events between scripts Weekly build: The system that makes the game a game. #### Week 10: Enemies or obstacles - Simple AI or patterns - Telegraphing - Fair hits - Pooling if needed Weekly build: Opposition that can be read and beaten. #### Week 11: Progression - Difficulty curve - Unlocks or waves - Fail states - Retry Weekly build: A reason to play the next minute. #### Week 12: Build 3 review - Mid-course playtest - What is actually fun - Cut list Weekly build: Build 3. Features freeze unless the tutor agrees. ### Month 4: UI, audio and animation Menus, HUD, sound and motion so the game reads as a product. #### Week 13: HUD and menus - Canvas - Health and score - Pause - Scene flow Weekly build: Menu, play, pause, fail, restart. #### Week 14: Animation - Animator or 2D frames - Transitions - Hit and death - Idle Weekly build: Player and main objects animate. #### Week 15: Audio - SFX - Music loop - Mix so UI still reads - One-shot vs loop Weekly build: The game sounds like a game. #### Week 16: Build 4 review - Feel pass - Missing juice - Accessibility of UI Weekly build: Build 4 content complete. ### Month 5: Polish and a real export Bugs, balance, and a build someone else can run. #### Week 17: Playtest protocol - Watch without talking - Written playtest notes - Three changes only Weekly build: Playtest notes and a change list. #### Week 18: Bugs and balance - Crash vs annoy - Difficulty - Checkpoints - Quit and resume Weekly build: The worst bugs closed. #### Week 19: Windows or Mac export - Build settings - Player settings - Icon - A folder someone can zip Deliverable: A build that runs outside the editor. #### Week 20: Build 5 review - Export checklist - Known issues list - Week 21 polish plan Weekly build: Release candidate 1. ### Month 6: Finish and show A playable game with a start, a middle, an end, and a build to take home. #### Week 21: Content lock - No new mechanics - Fill holes - Win and lose are clear Weekly build: Content locked. #### Week 22: Polish pass - Juice - Readability - Dead ends - Credits Weekly build: Polish pass on the live build. #### Week 23: Final export - Final build - Readme - How to play - Screenshot Deliverable: Final build and a how-to-play note. #### Week 24: Play session - Show the game - What you cut - What you would do next Deliverable: A playable finish you can show. ## What you need Online classes need this setup at home. In person classes are in Melbourne. Students still need a computer at home for homework. - A computer that can run a current Unity LTS release - Unity Personal, which is free - A reliable internet connection for live video - A microphone so the student can ask questions - Headphones if the house is noisy - Students under 16 join from a shared family space ## Who is Intermediate for? Students who have finished Beginner, or who already make small Unity games. Ages 12 to 14 is the usual band. ## Can they choose 2D or 3D? Yes. The tutor helps pick a scope that can finish in 6 months. ## What is a weekly build? A playable version at the end of each class. That is how progress is reviewed. https://www.gamedevacademy.com.au/courses/intermediate # Advanced Game Dev Course Ages 14 to 16. For students who have finished Intermediate, or equivalent Unity experience. For students who already finish small Unity games. They design architecture, write tools, profile performance and finish a portfolio piece. GST included: $250 per session, $1000 a month, $6000 in full. Online or in person in Melbourne, 2 hours a week for 6 months. ## What you finish with A portfolio piece with real architecture, a measured performance pass, and a build a stranger can run. - A project structured with data, services and scenes that can take new content - At least one editor tool or workflow that saved time - A profiler capture and a fix you can explain - A project archive a studio or university could open ## Week by week ### Month 1: Architecture for a larger student game Stop putting everything on the player script. Plan systems before they fight you. #### Week 1: What is already shipping - Audit a previous project - God scripts - Scene coupling - A portfolio target Deliverable: A written architecture note for the new project. #### Week 2: Bootstrap and scenes - Persistent managers - Additive scenes - Load order - DontDestroy pitfalls Weekly build: A boot scene that loads the game cleanly. #### Week 3: Data first - Scriptable objects - Tuning without recoding - Shared definitions - Folder rules Weekly build: Game data lives in Scriptable Object assets. #### Week 4: Build 1 review - Can a stranger open the project? - Naming - Scene map Weekly build: Build 1 with a project map. ### Month 2: Systems and editor tools Write the pieces other scripts talk to, and a small tool if it saves time every week. #### Week 5: Service boundaries - Audio, save, input as services - Interfaces where they earn their keep - FindObjectOfType as a smell Weekly build: One service used from two gameplay scripts. #### Week 6: Events - C# events - Scriptable object events - Who owns the raise - Unsubscribe Weekly build: UI and gameplay talk without dragging references across scenes. #### Week 7: A tiny editor tool - Menu item or custom inspector - Why this tool exists - Keep the tool small Weekly build: One tool that removes a weekly chore. #### Week 8: Build 2 review - Can you add a new enemy without editing five scripts? - Debt list Weekly build: Build 2 architecture review. ### Month 3: Gameplay depth Combat, traversal or multiplayer-lite, depending on the group and the project. #### Week 9: The hard mechanic - State machines - Hit detection - Authority of truth - Feel vs correctness Weekly build: The mechanic the portfolio piece is about. #### Week 10: Content pipeline - Prefabs as data - Variants - Spawn tables - Designers (you) can tune Weekly build: New content without rewriting systems. #### Week 11: Optional track - Lighting, or local multiplayer, or a bigger 3D space - Choose one track Weekly build: The optional track is playable. #### Week 12: Build 3 review - Feature freeze - What a studio would ask - Vertical slice Weekly build: Vertical slice. Feature freeze. ### Month 4: Performance and profiling Find frame-time spikes. Measure the cost and fix that. #### Week 13: Profiler - CPU vs GPU - GC spikes - Deep profile when needed - A baseline capture Deliverable: A profiler capture with three notes. #### Week 14: The first fix - Pooling - Update spam - Find in Update - Overdraw Weekly build: One measured improvement. #### Week 15: Build size and load - Addressables or simple load - Texture size - Log after load Weekly build: Load is boring and fast enough. #### Week 16: Build 4 review - Before and after captures - What you will not fix Weekly build: Build 4 with a performance note. ### Month 5: A portfolio piece Something you can show a studio or a university without explaining the homework. #### Week 17: What the clip shows - Thirty seconds of gameplay - Readme - Controls - What you built vs assets Deliverable: A one-page portfolio card. #### Week 18: Content complete - Start, loop, end - No debug leftovers - A quiet options screen Weekly build: Content complete. #### Week 19: Export for others - Windows or Mac build - Known issues - How to install Deliverable: A zip a stranger can run. #### Week 20: Build 5 review - Would you hire this student for a junior task? - Gaps Weekly build: Release candidate. ### Month 6: Ship and talk about it The last month is for finishing the project. #### Week 21: Lock - No new systems - Bugs only - Copy and UI Weekly build: Locked. #### Week 22: Final playtest - Someone who did not write it - Notes - Three fixes Weekly build: External playtest done. #### Week 23: Final build - Gold build - Trailer stills or a short capture - Credits Deliverable: Gold build. #### Week 24: Presentation - What the architecture did - What you would rewrite - Where this sits in a portfolio Deliverable: A portfolio piece you can show. ## What you need Online classes need this setup at home. In person classes are in Melbourne. Students still need a computer at home for homework. - A computer that can run a current Unity LTS release - Unity Personal, which is free - A reliable internet connection for live video - A microphone so the student can ask questions - Headphones if the house is noisy - Students under 16 join from a shared family space ## Who is Advanced for? Students who have finished Intermediate, or who already finish small Unity games. Ages 14 to 16 is the usual band. ## Is this a qualification? Game Dev Academy is not a registered training organisation. Advanced is a live class. Students finish with a portfolio piece. ## Do you teach multiplayer? Sometimes, if the group can finish it. Lighting or a larger 3D space are the other optional tracks. You pick one. https://www.gamedevacademy.com.au/courses/advanced ## FAQ ### What ages are the courses for? Beginner is 10 to 12, Intermediate 12 to 14, Advanced 14 to 16. A slightly older student who is new to Unity can start in Beginner. ### Are classes live or recorded? Classes are live, 2 hours a week for 6 months. Online classes are on video. In person classes are in Melbourne. If a student misses a class, they can watch it in the course portal. The tutor emails that week's task. ### What timezone are classes? Online classes run in Melbourne time, AEDT or AEST depending on the date. Overseas students join the live class at that Melbourne time. In person classes are in Melbourne. We confirm the class time when we offer a place. ### What computer do we need? Online classes need a computer that can run a current Unity LTS release, Unity Personal (free), a reliable internet connection, and a microphone. Headphones help if the house is noisy. In person students still need a computer at home for homework. ### How do I install Unity? Install Unity Hub, then a current LTS editor, before the first class. We email a short install note when we offer a place. Use Unity Personal. ### How big is a class? Classes are small live groups. Online, the tutor screenshares into each student's project. ### Can adults join? The syllabus is written for kids aged 10 to 16. An adult can apply. We will tell you if a group has a place. Adults join the existing groups. ### Can we study in person? Yes. Choose In person or Online on the apply form. In person classes are in Melbourne. We confirm the class time and venue when we offer a place. ### How do fees work? GST is included. You can pay per session, monthly, or in full. Each option is a payment plan for the full 6 month fee. See the fees page and the refund policy. ### Who teaches? Dinuka Jay, a senior Unity software engineer in Melbourne. 10 years of professional Unity development and 20 years of C#, including Melbourne Museum 3D, AR applications and mobile games. ### When is the next intake? Apply any time. We start a weekday or weekend group when we have enough students. We email the first class date when we offer a place. ### Can we leave mid-course? Each course is a 6 month commitment. After the 14 day window before the first class, the full fee is payable even if the student stops attending. Monthly and per session payments still have to be finished. Australian Consumer Law still applies. # Contact Unity courses online or in person in Melbourne, Australia. ## Email and phone study@gamedevacademy.com.au +61 450 210 940 Monday to Sunday, 10am to 6pm, Melbourne time. ## Applications Use the apply form for a course place. Creating a portal account does not enrol you. We read applications and then send a payment link if we can offer a place. ## Where we are Choose Online or In person on the apply form. Online classes run live on video for students in Australia and overseas. In person classes are in Melbourne. We confirm the venue when we offer a place. ABN 40 669 313 508 https://www.gamedevacademy.com.au/contact # Privacy policy This policy explains how Game Dev Academy collects and uses personal information. It applies to our website, applications, accounts and class communication. Last updated 13 October 2026. ## Who we are Game Dev Academy (ABN 40 669 313 508) of Melbourne, Australia, is the organisation that collects personal information through gamedevacademy.com.au. Email study@gamedevacademy.com.au or call +61 450 210 940. ## What we collect When you apply or create an account we collect name, email, phone number, whether the place is for a kid or an adult, year level if you tell us, course choice, how you want to study, how you prefer to pay, and any note you write. If you create an account we also store a login email, a password hash managed by our auth provider, and whether the account is for a parent or a student. We do not collect full card numbers. Payments are handled by Stripe. ## Why we collect it We use this information to read applications, offer places, send payment links, run classes, email the week's task if a student is away, and operate the parent and student portal. We do not sell personal information. We do not use it for unrelated marketing lists. ## Kids Our courses are designed for students aged 10 to 16. A parent or guardian should apply and hold the account for anyone under 18. We collect only what we need to run the class. For online classes, we ask families to join from a shared space at home. ## Payments Stripe processes course payments on our behalf, including the Craigieburn first class fee. Stripe's privacy policy covers card data. We receive payment status, the amount, and enough detail to match the payment to an application. ## Where data is stored Application and account data is stored with Supabase. Email is sent through our email provider. Those services may store data outside Australia, including in the United States. We choose providers that contract to protect personal information. ## Who we share it with We share information with the tutor running the class, with Stripe for payment, with our hosting and email providers, and if the law requires it. On the Craigieburn enrolment received page we send a lead event to Meta, and a purchase event when the first class fee is paid, described under Advertising measurement. We do not share student work publicly without permission. ## Advertising measurement If you submit the Craigieburn enrolment form, the next page on this website sends a lead event to Meta so we can measure Facebook and Instagram ads. That event includes the page address, browser type, IP address, and the ad click id when the form passes it through. When the form passes an email or phone number, we send Meta a hash of that value. The event does not include the student's name. When the $50 first class fee is paid on that page, we also send a purchase event to Meta with the amount and the currency. That event does not include the student's name. Meta's privacy policy covers how Meta uses these events. ## How long we keep it We keep application, enrolment and class records for as long as we need them to run the academy, meet tax and consumer law duties, and resolve disputes. You can ask us to delete an account. We may keep a limited record where the law says we must. ## Access and correction You can ask to see or correct the personal information we hold. Email study@gamedevacademy.com.au. We will answer within a reasonable time. ## Complaints Email us first. If you are not satisfied, you can contact the Office of the Australian Information Commissioner at oaic.gov.au. https://www.gamedevacademy.com.au/privacy # Enrolment terms These terms apply when you apply for or join a Game Dev Academy course. Last updated 20 September 2026. ## The agreement By submitting an application or paying a fee you agree to these terms, the refund policy and the privacy policy. If you apply for a student under 18, you confirm you are their parent or guardian and can enter this agreement for them. Each course is a 6 month place. Monthly and per session payments spread the full published fee over the term. ## The courses We teach Unity courses online or in person in Melbourne. Courses are Beginner, Intermediate and Advanced. Each runs part time over 6 months, 2 hours a week, on a weekday or weekend slot we confirm when we offer a place. Game Dev Academy is not a registered training organisation. Courses are not VET, university credit, or a qualification under the Australian Qualifications Framework. ## How you study You choose Online or In person on the apply form. Both use the same courses, hours and fees. Online classes are live on video in Melbourne time. The tutor shares the Unity editor. Students work on their own computer. Help is given by screenshare. You need a computer that can run Unity, a reliable internet connection, and a quiet place to work. Install Unity before the first class. In person classes are in Melbourne. We confirm the class time and venue when we offer a place. Students still need a computer at home for homework. ## Conduct Students must follow the tutor's instructions, keep language civil, and not record the class without our written permission. We can remove a student from a session or from the course for serious or repeated disruption. Leaving, or being removed for conduct, leaves the 6 month fee payable. Australian Consumer Law still applies. ## Student work The student owns the games they make. We may ask to show a project in an end-of-term play session or on the site. We will not publish a kid's surname or school without permission. ## Accounts A portal account lets you sign in. We offer a course place after we read the application. ## Changes by us We can reschedule a class, change the weekday or weekend slot, or move a group online if we cannot run a session as planned. If we cancel a course before it starts, we refund fees paid for that course. If we cancel a course after it has started, we refund the unused remaining fee. ## Fees and commitment A confirmed place is 24 classes over 6 months. After the 14 day window before the first class, you are liable for the full published course fee even if the student stops attending. Cancellation in writing at least 14 days before the first class is covered in the refund policy. Choosing monthly or per session does not reduce the total. Stopping a Stripe payment does not cancel the remainder. We can invoice the unpaid balance. ## Australian Consumer Law Nothing in these terms limits your rights under the Australian Consumer Law. If a term would be unlawful, it is read down or dropped, and the rest still applies. Victorian law applies. The courts of Victoria have jurisdiction, without limiting any ACL rights you have in your own state or territory. https://www.gamedevacademy.com.au/terms # Refunds and cancellation Each course is a 6 month commitment. Monthly and per session are payment plans for the full published fee. This policy sits with your rights under the Australian Consumer Law. Those rights are not excluded. Last updated 20 September 2026. ## The 6 month place Beginner, Intermediate and Advanced each run 24 classes over 6 months. After the 14 day window before the first class, you are liable for the full published course fee, including GST, even if the student stops coming. ## Before the first class Email study@gamedevacademy.com.au from the address on the application. Say the student name and the course. If you cancel in writing at least 14 days before the first class, we refund the course fee we have taken. ## Once that window has passed Withdrawing after this window does not reduce the remaining fee. Unused months and unused sessions stay payable. If you paid in full, that payment stands. If you pay monthly or per session, the remaining instalments stay due. Cancelling, pausing, or failing a Stripe payment leaves the balance payable. We can invoice what is still owed and recover it. Removal for serious or repeated disruption leaves the remaining fee payable, subject to Australian Consumer Law. ## Missed classes If a student misses a class, they can watch it in the course portal. The tutor emails that week's task. ## If we cancel If we cancel a session, we make it up or refund that session's share of the fee. If we cancel a course before it starts, we refund fees paid for that course. If we cancel a course after it has started, we refund the unused remaining fee. ## How refunds are paid Where a refund is due under this policy or the Australian Consumer Law, it goes back to the original Stripe payment method. Allow 5 to 10 business days after we confirm. Stripe's timing can add a few days. https://www.gamedevacademy.com.au/refunds