How bruno-pezzolo/ggj2016-therapy works
Main Components
• Scenes – there are multiple scenes such as “Splash”, “Scene 1”, “Scene 2”, “Scene 3”, and “Scene 4”. Each scene can be represented as a module/state of the overall game.
• Game Logic & Behavior Scripts – present in various folders (Assets/Scripts, Assets/Scene 1/Scripts, etc.). These include components for player controls, collisions, audio triggers, and level-specific interactions.
• Prefabs – reusable game objects (e.g., Car, Player, AudioPoint, TraumaSource) that are used across scenes.
• Audio/Multimedia Assets – that supply sound effects and background audio (scene-specific sounds under each scene folder, Materials for visuals, etc.).
Relationships and Interactions
• The Unity Engine sits at the heart, managing the lifecycle of Scenes and game objects (actors).
• The Splash Scene typically acts as the introductory module that triggers transitions to the main game scenes.
• Each scene hosts its own set of scripts that handle specific game logic. For example, Scene 1 has scripts like DadStep1.cs, DadStep2.cs, etc., indicating a narrative or step-by-step progression.
• The game objects (created from prefabs) are linked to behavior scripts (such as CarMovementScript, PlayerInteraction, ProximitySensorScript) and interact through Unity’s event system.
• Audio is integrated across scenes (notably different folders for sounds per scene), which ties into both the prefabs and the game logic through dedicated sound manager scripts.
• There’s interdependency with Standard Assets libraries that manage character controls, camera behavior, input, and physics.
Architectural Patterns and Design Principles
• Component-based architecture is central. Each game object is composed of one or more components (script behaviors, audio sources, colliders, etc.), which should be clearly noted.
• The game follows a scene-based state management approach; each scene is essentially a level or a narrative component.
• Use of prefabs indicates reuse and an emphasis on maintainability.
• The segregation of scene-specific assets and global utilities (via the Standard Assets folder) shows a separation of concerns.
Relevant Technologies and Frameworks
• Unity Engine
• C# scripting (for gameplay, collision, interaction, and audio management)
• Unity’s built-in modules for physics, audio, and scene management
• Third-party or standard libraries for cross-platform input (as seen in the Assets/Editor/CrossPlatformInput and Standard Assets/CrossPlatformInput)