How x2shadow/escapefromcandytower works
The “Escape from Candy Tower” project is a Unity-based 3D Platformer. Its architecture is built on top of Unity’s game engine using the Universal Render Pipeline (URP) with several plugins and external assets to extend functionality (such as GamePush for online features, UniTask for async capability, the NEW Input System for improved player input, and the Safe Area Helper to manage UI on multiple devices).
Major Components
• Game Engine – At the heart of the project is Unity. Indicate Unity’s core systems (rendering, scene management, physics, etc.) since the project relies on Unity 2022.3.55f1 with URP.
• Scenes & Levels – The project includes multiple Unity scenes (Level1, Level2, Level3, MainMenu) which organize game flow and user experience.
• Game Logic & Managers – Look for key scripts and prefabs such as GameManager, AudioManager, CameraManager, PlayerController, and supporting managers (e.g., for checkpoints, UI, input handling).
• Assets & Art – There is a significant collection of art assets, 3D models, animations, materials, and prefabs (characters, platforms, environment objects) that define the visual and interactive aspects of the game.
• Input & UI – The project uses the new Unity Input System and TextMesh Pro, with dedicated scripts and prefabs for UI elements such as buttons, sliders, and on-screen feedback.
• Audio – An audio sub-system is indicated through AudioManager, audio prefabs, and relevant sound effect files.
Relationships and Interactions
• Unity Engine as the base platform and indicate that it hosts various subsystems (Scenes, Physics, Rendering, Input).
• Dependencies from game logic components to the plugin modules. For example, runtime game scripts interact with GamePush for online communications or achievements.
• Pull in the relationship between the UI layer (using TextMesh Pro, safe area management) and input systems.
• Asynchronous operations and external calls using UniTask, highlighting how gameplay scripts interact with these utility libraries for non-blocking operations.
• Out how art assets (3D models, animations, prefabs) are loaded into the scenes and manipulated by the logic scripts (for example, during character movement, collision detection, platform mechanics).
Architectural Patterns/Design Principles
• The overall design follows Unity’s component-based architecture where each game object has attached scripts (MonoBehaviours) handling discrete functionality.
• There’s a separation of editor (setup windows, game configuration editors under Editor folders) and runtime code (under Runtime folders).
• Many modules are organized in a modular fashion (for example, under the GamePush/Runtime/Modules directory) which suggests an emphasis on reusability and separation of concerns.
• Use of asynchronous programming with UniTask is a design choice to improve responsiveness and decouple heavy operations.
• Component is clearly labeled (e.g., “GamePush Runtime”, “UniTask Library”, “New Input System”) with explanations of roles.