How ctrl-games-dev/under-control works
Based on your file tree and the README, this project is a Unity game (specifically “Under Control a T3G game from CTRL Games”) built on the UnityEnginePlatform. Although the README is brief, the detailed file structure reveals that it is a fairly complete game project that leverages many of UnityEnginePlatform’s features such as scenes, prefabs, a wide variety of assets (animations, audio, textures, models), scripting for game logic (AI, inventory, UI, etc.), and third-party plugins (like DOTween).
Main Components
• Scenes: Include major scenes such as Adventure, Boss, Hub, MainMenu, and various workspaces. These are the levels or game states.
• Prefabs and Assets: Group together prefabs (for UI, characters, enemies, environmental elements) and resources such as FBX models, textures, materials, animations, and audio.
• Scripts: Highlight key scripting layers. For instance:
• Game Management (GameManager, Scene/Level Managers, MainMenuManager)
• UI Systems (HUD, Inventory, PauseScreen, HoverTooltip)
• AI Components (BoarAI, BoarBoss, enemy behaviors, actions)
• Player Control (PlayerController and related player scripts)
• Inventory and Item Systems (Inventory scripts, item datas, and item entity handling)
• Visual and Audio Effects (VFX, WeaponTrail, MusicPlayer)
• External Dependencies: Include third-party toolkits such as DOTween from Demigiant.
• Settings and Project Configuration: Represent the ProjectSettings (e.g., Input, Physics, Graphics) which configure core behavior.
Relationships and Interactions
• Directional data flows from the UnityEnginePlatform as the foundation interacting with all components.
• That the GameManager acts as the central orchestrator connecting:
• Scene and Level Managers: these load and manage different scenes (Adventure, Boss, Hub, etc.).
• UI components: for in-game interactions and menus.
• Inventory and Item systems: managing player inventory, interactable objects, and pickups.
• Link AI and player scripts to their related animations, prefabs, and behavior graphs.
• That prefabs (characters, enemies, environmental objects) are constructed in UnityEnginePlatform and then manipulated by their corresponding scripts.
Architectural Patterns and Design Principles
• The project is structured in a modular way where each feature (AI, Inventory, UI, Levels) is in its own set of directories under Assets/Scripts.
• Use MVC-like separation: where game data (such as ScriptableObjects for Items, Guilds, and Effects) are decoupled from the logic that manipulates them.
• Event-driven communication using central systems like the EventBus.
• Use of dependency injections or manager classes (GameManager, HubManager, etc.) that coordinate interactions between loosely coupled systems.
Relevant Technologies and Frameworks
• That the project runs on UnityEnginePlatform (as required, using that exact string).
• DOTween is used for tweening animations and smooth transitions.
• Other built-in Unity systems such as NavMesh, audio mixers, and timeline/post-processing effects are managed through ProjectSettings.
• ScriptableObjects are used extensively for managing data (items, spells, AI behavior, and game context).