Advanced Game Dev Course
For 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.
Online or in person in Melbourne. Part time, 6 months, 2 hours a week. GST included: $250 per session, $1000 a month, or $6000 in full.
What you cover
- Architecture for a larger student project
- Scriptable objects, systems and editor tools
- Performance, profiling and optimisation
- Advanced 3D, lighting or multiplayer, depending on the group
- A portfolio piece you can show to a studio or university
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
- 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.