How drewlickman/code-runner works
Main Components
• Game Engine/Core: Represent the Unity Engine itself with its built-in subsystems (rendering, physics, input handling, etc.). This is the underlying runtime that connects all other parts.
• Scenes: These are the individual game levels and menus. The file tree shows several Unity scene files (e.g., MainMenu.unity, Level 1.unity, Boss Arena.unity, GameOver.unity, Victory Screen.unity). They represent different game states and environment layouts.
– Animations: Contains controllers and animation files for both player and multiple enemy types.
– Audio: Background music, sound effects for player actions and enemy interactions.
– Sprites & UI: Visual assets for enemies, players, UI elements, and menus.
– Terrain & Prefabs: Environmental components, level geometry, obstacles, traps, and reusable prefabs (for player, enemies, and interactive objects).
– Scripts: Organized into areas like “Enemies” and “Player,” these govern the logic and behavior of game elements (player movement, enemy behavior, game timers, and trap logic).
Relationships & Interactions
• Scenes load and instantiate Prefabs (players, enemies, traps, UI, etc.) dynamically, so illustrate connections between Scenes and Prefabs.
• The UI system (under Assets/UI and Prefabs/Player) sends and receives events (like player input and game state changes) to/from Game Manager scripts and other controllers.
• Also denote how Physics (triggering collision detections, movements, and interactions) is encapsulated within the Unity Engine, affecting both player and enemy components.
Architectural Patterns & Design Principles
• Prefab Reuse: Demonstrate the use of prefabs to build game objects (obstacles, enemies, UI elements) which are instantiated across various Scenes.
• Separation of Concerns: Scripts are grouped by functionality (Enemies, Player, Timer, etc.) which aligns with MVC/MVVM style separation even though Unity’s architecture is less formal.
• Asset-Driven Design: The organizational structure of assets (Images, Terrains, Audio, etc.) directly influences visual and interactive components of the game.
Technologies and Frameworks
• Unity Engine as the core framework.
• Unity’s built-in physics, input, and rendering systems.
• Use of Unity’s UI Toolkit for menus and in-game UI.
• Potential integration of Text Mesh Pro for enhanced text rendering (as seen in the Assets/TextMesh Pro subfolder).