A standard class we often see in Unity projects is the Game Manager. It's usually implemented as a Singleton by developers, but its responsibility varies from one code base to another. Some programmers use it to manage top-level game states or as a globally accessible front-facing interface to core game systems.
In the context of this chapter, we will give it the singular responsibility of managing a game session. Similar to the concept of a game master in board gaming, it will be responsible for setting up the game for the player. It can also take on additional responsibilities, such as communicating with backend services, initializing global settings, logging, and saving the player's progress.
The critical thing to keep in mind is that Game Manager will be alive for the entire lifespan of the game. Therefore, there will be a singular but persistent instance of it in memory at all times.
The following diagram illustrates the overall concept:
