Architecture
This will be a 2D game developed in Unity using C# as the programming language. The following libraries, frameworks, and services will be used:
-
Unity Engine: The core framework for building the game, handling the physics, animations, input, and rendering of 2D sprites and environments.
-
Unity UI Toolkit: Used to create and manage in-game user interfaces such as menus, HUD, and dialog systems.
-
Unity 2D Physics: Responsible for implementing the game's physics, including collision detection and responses for game objects.
-
Unity Animation System: Will be used to create smooth transitions and movements for characters and objects using 2D sprites.
-
Cinemachine: A camera system for smooth camera movement, zoom, and tracking of characters during gameplay.
-
Unity Input System: To handle player input for both keyboard and game controller setups.
-
TextMeshPro: For rendering high-quality text in the game UI and dialogues.
-
Unity Addressable Assets System: To manage and load assets effciently, allowing for dynamic loading of levels, characters, and other game assets.
-
Unity Analytics: To collect player data such as gameplay statistics, user engagement, and behavior in the game to inform design decisions.
The Unity package manager is what we will be using as our package/build manager.
We will use a binary exe file, As Unity allows you to directly compile projects in exe files. Testers will then be linked to a separate Github Repository containing this executable.
Example of the title screen of the game would look like. Having both the options button and start button, it sets out what it is suppose and shows the basics of what a title screen should be. Simple and effective for the tester/player to understand what to do.
A waiting/lobby room for players to wait for others to join them. You can ready up at any time with any amount of players and can go in alone, or with other people.
Example of what a the main game would look like with player in the middle, inventory in the bottom right, and health/oxygen meter top left, and the stamina meter is in the top left as well. It gives a good idea of what the game will look like from players/testers perspective.
Another example of what the main game would like with player picking up an "artifact" having inventory in the bottom right, oxygen and stamina in the top left and player in the middle.
Example of what the pause menu would like look in game, it would have resume to continue playing, settings, and a quit button, while you have this menu opened in multiplayer this shouldn't affect other players.
This is an example of the settings menu having options for changing your volume, adjusting how loud you want the game to be, and controls so that the player/tester can suit their playstyle if they need to.
This is example of "game over" screen in the game if you run out of health, it shows that once you die you can only go to the main menu in order to play another game.
Example of what a building would look like in game. It would appear underwater and you would have to interact in order to enter it. It is an example of an area in a game where you would go to collect artifacts.
Joshua Kolbusz: Issues #45, #47, #48, #49, #51, #52
Kelly Thao: Issues #34, #33, #32, #27, #26, #22, #21
Scott Do: #59, #44, #43, #42, #39, #37, #36
Tristen Fornes: #28, #29, #30, #31
Tyler Stargel: Issues #35, #38, #40, #41, #46, #50, #53, #54, #55, #56, #57