Managers

Overview

Managers exist to give the project a clear runtime entry point. The scanned project contains GameManager, InputManager, SoundManager, LoadingSceneManager, KillsManager, SaveLoadManager, GameSettingsManager, LevelManager and TimeManager.

Rules

• A manager owns one high-level responsibility.
• A manager is not a place for random gameplay logic.
• If a smaller system can own the behavior, keep it there.

Common mistake

[!WARNING] Do not turn InputManager or UIManager into a catch-all singleton for unrelated features.

Media Suggestions

• Screenshot: Bootstrap object with manager components.
• Screenshot: Inspector showing InputManager maps and state references.
• GIF: Pause, dialogue and gameplay switching.
• Video: Manager responsibilities explained with examples.
• Diagram: Manager layer above the feature modules.