Architecture

Game Manager

The game manager is a crucial part of any game development project. It is a script or a set of scripts that typically acts as a high-level component, overseeing other components and managing their interactions with one another. The game manager is responsible for managing various aspects of the game, such as input, sound, graphics, game rules, scoring, and more.

In Unity, the game manager component is usually written in C# or another programming language and includes methods and properties for controlling various aspects of the game. For example, the game manager might include methods for starting and stopping the game, keeping track of the player's score, handling user input, and managing game objects and their interactions.

The game manager ensures that the various components of the game work together seamlessly, providing a satisfying experience to players. By managing the game's different components, the game manager helps to ensure that the game is engaging, entertaining, and easy to play, ultimately enhancing the overall experience for the player.

Game Manager

The game manager these components are responsible for a variety of tasks such as creating and managing game objects, handling the game's main logic (e.g. determining win/loss conditions and detecting when the game is over), activating and deactivating other managers as needed, and more. In short, the game manager plays a critical role in ensuring that all the various components of a game work together seamlessly and that the game delivers a satisfying and engaging experience to players.

The Food Manager

Object Pool, Singleton

The Food Manager component is responsible for spawning and managing the Food Object. Every few seconds, the manager checks the number of objects in the game room and adds a new object if it's possible. If there are no objects available in the pool, the manager creates a new object. In addition, the manager is also responsible for managing the effects pool, ensuring that effects are applied appropriately and efficiently.

The Chaos Manager

The Chaos Manager is a core component of the game responsible for managing all the objects in the environment that contribute to the game's chaotic atmosphere. This includes objects like rising water levels and various non-player characters. Essentially, the manager is responsible for overseeing all objects that are not directly controlled by the player or related to food collection, ensuring that they function properly and contribute to the overall gameplay experience. By managing these objects effectively, the Chaos Manager helps to maintain the flow and pacing of the game, keeping it engaging and challenging for players without creating unnecessary technical issues. Overall, the Chaos Manager plays a critical role in creating a sense of unpredictability and excitement in the game.

Player

In Unity, the "player" is the game object that represents the main character in a game. It contains all the logic and components needed to control the character's movements and interactions with the game world. The player object typically includes components such as transform, rigidbody, collider, script components, animation, and input manager. Overall, the player object is a crucial component of any game project, providing the means for players to interact with and explore the game world.

Player

The player is made up of several components that handle user input and provide feedback to the user. This includes managing animations, updating the player's life and power scores, and responding to gameplay events. The player acts as a bridge between the user and the game mechanics, translating user input into game actions and providing visual and audio cues to the user. Effective management of these responsibilities is crucial to creating a smooth and immersive gameplay experience for the user

The Player Action Hand is a key component of the player object, containing a state machine designed to handle the different states that the character's hand can be in.

This helps to create a clear separation between the logic of each possible state, making it easier to manage and update the code as needed. Specifically, the character's hand can be in one of four possible states: Free, Holding food but not charging, Powering force to throw, and Throwing the food.
The state machine stores an array of all the possible states and an index of the current state. Whenever a function or event is triggered, the script activates the current state to handle it. By effectively managing the player's hand states, the game can provide a more seamless and intuitive user experience.

- The IStateMachine<T, TIndex> is a generic interface created for when T represents the states that must implement the IState interface. TIndex is used to represent the way to access the current state of the machine.
- MonoBehaviour is the base class that every game object in Unity inherits from.
- IState is a generic interface used for state for the so-called states.
- IStatePlayerHand is a concrete interface for the state machine of the player's hand.

Food

Similar to many games, our game contains weapons and allows players to collect them. However, unlike other games, our weapons are disposable and cannot be stored. Players can use them and then throw them away.

The Thrown state in 'Dining Combat' is similar to the throwing mechanism in 'Angry Birds,' where the player aims and launches the food item towards the opponent, inflicting damage upon impact.
The normal type is displayed by any food that only performs its effect and takes away a life from the player when it hits them.

Creation

builder

The manager can construct objects by holding a prototype of each object and choosing to create them as needed. Each object is a small state machine which enables it to determine what action to take.

For each object, there is a special state called the 'Thrown State'.

Object Pool Entry

When an object enters the pool, it becomes inactive.

State Thrown

A special state for each object type, used when the object is thrown.

Object Pool Wait

The object waits in the pool until the manager retrieves it and assigns it a destination.

State Collected

The player has collected the object.

State Uncollected

The fruit has not been collected and can be picked up. This is the only state in which the player can collect the fruit. This mode is designed to prevent players from taking fruit in another mode.

Chaos

The game has several different features to create a sense of chaos for the players. Some parts are interactive for the player, while others are not

Currently in the process

We want to add characters that create chaos and affect the game flow, such as a flying chicken that randomly lays eggs. If the eggs hit the player, it will reduce their life points. Additionally, a corn on the cob with legs will run around the room and explode at random times. Catching it will grant points and allow the player to throw it, similar to the golden snitch in Quidditch from Harry Potter

Dining Combat

Architecture

Game Manager

Game Manager

The Food Manager

The Chaos Manager

Player

Player

Movement

W

A

D

mouse

S

Free State

Holding State

Powering State

Throwing State

Food

FoodManget

FoodPool

EffectsPool

Entr / Exit

FoodObject

State Food

Entr / Exit

State Thrown

Collected

Uncollect

Player-Hand
free

Player-Hand holding

Player-Hand
throwing

Player-Hand charging

Builder by type

Weapon

Food Objects

Chaos

Subscribe for News and Updates