Try it on itch.io from your browser!
A clone of a simple 2D arcade shooter, made in Unity.
Developed as a homework for the Mobile course of the Master in Computer Game Development.
It features almost every basic game development element (player controller, animations, collisions, items, game state, UI).
Learn the basics of Unity development by replicating the game Pang.
As a simple 2D arcade game, it was a simple–yet complete–example,
requiring the implementation of various details, spanning almost the entire essential Unity toolset.
Being a mobile course, the project had to be developed with a mobile-first strategy in mind, so touch input alternatives were required.
An emulated web version of the game is available here for a comparison with the original game.
The game can be played from the browser from the itch.io page. Otherwise it's available there for download as an Android application too.
The game is made up of three levels (called stages) and each has its own scene in Unity.
The startup scene though is MainMenu,
which is used to start a new game for the first time, or after a Game Over (both win or lose).
The game can be played with keyboard or gamepad, as well as with touch controls designed for mobile devices.
- Move left/right and climb: Arrows/Left stick/D-Pad
- Shoot: S/Space/Left gamepad button
- Move left/right: touch areas on the screen
- Shoot: central weapon button
- Climb: up/down buttons when near ladders
While working on this project I had to learn many aspects of Unity development for the first time. As all first-time projects, many parts of this game were written before I learned more structured and elegant development patterns, so don't expect to find anything well-polished or consistent.
Below I list the most relevant topics I worked on this project:
- Unity's prefab/hierarchy: very useful when mastered, can be used to achieve a great re-use of game elements
- Basic sprite animations
- Rigidbody collisions
- Trigger collisions: these are still not totally clear to me.
They seem too much "exploitable", allowing a wide variety of use-cases.
The line between trigger and collision is sometimes slightly blurred. Also, I couldn't find an elegant pattern to manage layer filtering. - Player controller: this was much harder than expected.
The final result is a mess and the part I'm least proud of.
Handling climbing movement and Y-axis positioning in general was a real pain, and there are still strange bugs hanging around (mostly concerning ladders). - UI
- Input, using the new Input System
- Global game state: I'm not sure how much I'm supposed to use singletons and global state in general. I found out about events later in the project and realized they are a much simpler and elegant solution. OOP feels very limited in Unity's game object model.
- Sprites: Player, Items/Misc
- Font: Departure Mono
- Up/Down buttons icon: Up by Disha Vaghasiya on Flaticon
- Bubble pop sound: Sound Effect by freesound_community from Pixabay