Intermediate Game Dev Course
For 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.
Online or in person in Melbourne. Part time, 6 months, 2 hours a week. GST included: $200 per session, $800 a month, or $4800 in full.
What you cover
- Planning a small 2D or 3D project
- Weekly builds, planning and polish
- Animation, UI and audio
- Exporting a build for Windows or Mac
- Scope, polish and a playable finish
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
- 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.