Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 36 ยท Projects and Practice

Unity Practice Exercises and Next Steps

Consolidate your Unity skills with graded exercises on UI, input, animation, audio, 2D and 3D, optimization and publishing, plus game ideas, a portfolio plan and what to learn next.

You now know the major parts of Unity: the editor, C# scripting, physics, UI, input, animation, audio, 2D and 3D workflows, optimization and publishing. Reading is not enough. Game development is learned by finishing small games. This lesson gives you graded exercises, runnable logic exercises you can try on this page, project ideas, a portfolio plan and a map of what to study next.

Unity itself does not run on this site. The editor exercises are described for you to do in your own Unity install; the logic exercises have runnable C# starters.

How to practice

  1. Finish small. A complete one-room game beats an unfinished open world.
  2. Time-box. Give each exercise a deadline (an evening, a weekend).
  3. Use version control from day one (Git, with a Unity .gitignore).
  4. Profile and test on a device at least once per project.
  5. Show your work. Share builds (itch.io is free for WebGL and desktop) and ask for feedback.

Editor and component exercises

Level 1: basics

  1. Make a coin that spins (Animation window), plays a sound and disappears when touched, and increments a TextMeshPro score.
  2. Build a main menu with Play, Options (volume slider via an AudioMixer exposed parameter) and Quit; the Play button loads a second scene.
  3. Create a door that opens with an animation and an animation event that plays a creak sound.
  4. Switch a small prototype from the old Input Manager to the Input System with a rebindable Jump action.

Level 2: systems 5. Add coyote time and jump buffering to your character and compare the feel with and without them. 6. Make a health bar (UI Slider or UI Toolkit element) that animates smoothly toward the new value instead of snapping. 7. Build a 2D level with a Rule Tile, a Composite Collider and parallax backgrounds. 8. Make an enemy with Patrol, Chase and Attack states using a NavMeshAgent in a 3D arena. 9. Replace all bullets in a prototype with an ObjectPool<T> and confirm with the Profiler that allocations dropped.

Level 3: complete projects 10. A complete game from this chapter: platformer, top-down shooter or endless runner, with a menu, pause, game over, saved high score and a WebGL or Android build. 11. A game jam entry: pick a theme, plan scope for 48 hours, and publish it.

Logic exercises you can run here

The following starters run in plain C#. Solve them, then port the idea to a MonoBehaviour.

C# Exercise 1: smooth health bar

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with Console.ReadLine()), it gets the next line from this box.

C# Exercise 2: cooldown tracker

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with Console.ReadLine()), it gets the next line from this box.

C# Exercise 3: inventory with stacks

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with Console.ReadLine()), it gets the next line from this box.

Game ideas by size

  • Tiny (1-3 days): pong with a twist, breakout, a memory card game, a clicker with upgrades, a whack-a-mole with combo scoring.
  • Small (1-2 weeks): a tower defense with three tower types, a match-3 puzzle, a physics puzzle (Angry-Birds-style), a roguelike room crawler, a farming sim slice.
  • Medium (1-3 months): a metroidvania map with abilities gating areas, an RPG with dialog and inventory, a racing game with ghost laps, a card battler with ScriptableObject cards.

Building a portfolio

  • Three finished, polished games beat ten prototypes. Include one 2D and one 3D, and one with a build players can try in the browser.
  • Record 30-second GIFs or videos, write a short post-mortem (what went well, what you would change), and keep the source on GitHub.
  • Show technical depth in one area: shaders, tools for designers (custom editors), procedural generation, networking or AI.

What to learn next

  • Architecture: ScriptableObject-based data and events, dependency injection, state machines, the Command and Observer patterns.
  • Graphics: Shader Graph and HLSL, VFX Graph, URP renderer features, lighting techniques.
  • Performance: the Job System, Burst, ECS/DOTS (Entities) for thousands of entities.
  • Multiplayer: Netcode for GameObjects, Unity Gaming Services (Relay, Lobby), or Mirror and Photon.
  • Platforms: XR (OpenXR, XR Interaction Toolkit), console requirements, store optimization and live-ops.
  • Tooling: editor scripting (custom inspectors, Editor Windows), automated tests with the Unity Test Framework, CI builds.
  • Fundamentals: C# (see the C# tutorial), math for games (vectors, matrices, quaternions), and design (game feel, level design, balancing).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the best way to build skill as a game developer?

    Finishing small projects teaches the whole loop from idea to published build.
  2. 2. In Exercise 1, what prevents the health bar from overshooting the target?

    Clamp the movement to the remaining gap, as Mathf.MoveTowards does.
  3. 3. Where can you share a WebGL game for free so others can try it?

    itch.io hosts HTML5 builds and is popular for jams and portfolios.
  4. 4. Which topic helps when you need thousands of simulated entities?

    Data-oriented design and parallel jobs scale to very large entity counts.

Summary

  • Learn by finishing small projects; time-box, use version control and share builds.
  • Work through the graded editor exercises, the runnable logic starters and the full projects.
  • Build a portfolio of a few polished games and add depth in one specialty.
  • Keep growing with architecture, graphics, performance, multiplayer, XR and tooling.

Next: Back to the Unity track