How stochastis/vugamejam works
Project Type and Purpose
• This is a Godot Engine–based game jam project.
• The primary entry point is main.tscn, and the project configuration is in project.godot.
• The README focuses on Git branch workflow guidelines rather than architecture, so most domain logic lives inside Godot scenes and scripts.
Main Components
a. Godot Engine Core
• Scene system (nodes, instancing)
• Rendering & physics subsystems
• Input and audio subsystems
b. Project Scenes
• main.tscn (entry point scene)
c. Key Node Hierarchies & Scripts
• Player node (and associated Player script)
• Enemy or NPC nodes
• UI nodes (HUD, menus)
• Game manager or singleton (AutoLoad) for global state
d. External/Build Components
• Git repository (branches, CI if any)
• Export targets (desktop, web, mobile)
Relationships and Data Flows
• Physics engine feeding collisions back into gameplay logic.
• How the Game Manager communicates with scenes (loading/unloading, score tracking).
Architectural Patterns & Design Principles
• Scene inheritance or composition (e.g., a BaseEnemy scene instanced by each level).
• Singleton/AutoLoad for shared state or managers.
• Separation of concerns: UI nodes handle display only; gameplay scripts handle logic only.
Technologies, Frameworks, Libraries
• Godot Engine (version as specified in project.godot)
• GDScript (or C#) scripts attached to nodes
• Any community plugins (audio, pathfinding) you recognize in project.godot or .tscn files
Capturing Essential Architectural Elements
• Don’t overload: focus on key scenes and nodes that drive gameplay.
• How the Godot engine operates as the runtime host.
• How developers interact via Git (branch → PR → main), even if informally, to close the loop on collaboration.