Conor MacCarthy - 100876374
This Unity project was created by me in its entirety
This game is a small, first person shooting range. The player can walk around a small playable area. There are some buttons that the player can shoot to change the difficulty and a start button. Shooting the start button causes a number of targets to appear one after another. The goal for the player is to shoot the targets as many times as possible to get a high score. 5 targets will spawn, at which point the player must shoot the start button again to try again, which resets their score.
Controls:
- WASD - Move
- M1 (Left click) - Shoot
The project uses the following assets from the Unity Asset Store:
- https://assetstore.unity.com/packages/3d/environments/landscapes/low-poly-simple-nature-pack-162153
- https://assetstore.unity.com/packages/2d/textures-materials/sky/fantasy-skybox-free-18353
This project demonstrates use of the following design patterns: Singleton, Observer, Command, Factory, Object Pooling. Below is a brief description of where in the project each pattern has been implemented:
- Singleton: The UI Manager is a singleton. It controls the score displayed, as well as the current difficulty.
- Observer: The UI Manager observes the Player Controller. When the player shoots a target, the UI Manager is notified and increases the score by 10.
- Command: When the difficulty is raised or lowered, the requests are passed as command objects to an invoker. The invoker executes the command to increase the difficulty, and undoes the command to lower the difficulty.
- Factory: There are 3 concrete factories corresponding the the 3 target types (small, medium and large). When the start button is shot, the factory corresponding with the current difficulty spawns targets one at a time. Targets are spawned in random locations by the factory, and the factory also tells the targets to start moving. The specific logic for movement is unique for each target type.
- Object Pooling: There is a meteor shower constantly ongoing above the playable space. The meteors are all instantiated at runtime, and are placed into an object pool. There is a spawner object that takes a meteor from the pool every 0.1 seconds, spawns it in a randomized location, and causes it to move across the sky, at which point it is deactivated and returned to the object pool.
Below are UML diagrams for each design pattern I have implemented into the project (for each diagram, most of the functionality for some classes has been omitted, leaving only the essential fields and methods for understanding how the pattern works):
Singleton:
Observer:
Command:
Factory:
Object Pooling:
Scene Preview:
