How sakurai8080/party_game works
Main Components
• Game Manager & Core Systems: Represent central controllers like the GameManager (in Manager folders), NameLifeManager, and GameSetupUtility which orchestrate overall game flow.
• Mini-Game Modules: There are several dedicated mini-game modules (e.g., BallGame, BombGame, Dice, RouletteGame, SecondsGame, TheButtonGame). Each module is structured with its own Managers, UIs, and Scripts, so these should be individually represented.
• MVP Layer Structure: Since the project uses the MVP pattern, show the separation of concerns:
• Model: Data assets (ScriptableObjects in the ScritableObject folder, TweenData, and other game state information).
• View: Unity Scenes, Prefabs, UI elements (under Scenes, Resources/Prefabs, UI Toolkit assets, and UIs folders).
• Presenter: Scripts that act as coordinators between the model and view (located in each module’s UIs and parent Scripts folders like PresenterBase, BallUIPresenter, BombUIPresenter, etc.).
• Resource Management: Include separate nodes for Assets like audios (Audios, SE, BGM), materials, fonts (TextMesh Pro Resources under Assets/AssetStoreTools/TextMesh Pro), and textures.
• External Plugins & Libraries: DOTween (in Assets/Plugins/Demigiant/DOTween) for tween animations and TextMesh Pro for advanced text rendering.
• Configuration & Project Settings: Unity’s ProjectSettings and Packages (manifest.json, etc.) nodes can be abstracted as configuration/environment for the system.
Interactions and Relationships
• Resource Access: Show that audio components, animations (DOTween), and text rendering (TextMesh Pro) interface with the game and UI components.
• Scene Transitions: Demonstrate how different Scenes (Title, MainScene, GameSelect, mini-game scenes like BombGame.unity, Dice.unity, etc.) transition through central controllers and managers.
Architectural Patterns & Design Principles
• MVP Pattern: Clearly group components in three layers to illustrate separation of concerns.
• Modularity: Each mini-game component (BallGame, BombGame, etc.) is largely independent with its own dedicated folders, managers, and UI scripts. Represent these as modules that plug into the larger game framework.