How image-campus-2025-trayecto-godot/clase-13 works
Project type and purpose
• This is a 2D platformer game built with the Godot Engine.
• There is no server or database; it is a standalone game application.
• Key features: scene-based game elements (player, enemies, props), UI screens (menus, levels, HUD), global managers, resource packs (Kenney assets), and two Godot plugins (ruake REPL and slides).
File structure
• Top-level folders:
• addons/ruake and addons/slides – in-editor plugins (REPL, presentation slides)
• assets/… – imported audio and graphics from Kenney asset packs
• globals/ – singleton scenes and scripts (GameState, LevelManager)
• resources/ – .tres files for themes, tilesets, label settings
• scenes/ – all game scenes, subdivided into game_elements/enemies/props, hud, screens (levels, menus), ui
• Configuration files: project.godot, game_settings.gd, plugin.cfg in each addon
• Build/deployment: handled by Godot’s export system (no custom scripts)
README
• (Empty in this case; structure implies Godot conventions)
• Plugins are standard Godot addons; no additional architecture notes.
Diagramming conventions
• “Engine loads → Global Singleton”
• “LevelManager triggers → Level Scene”
• “Player interacts → Physics Engine”
• “Scenes request → Asset/Resource”
• Game logic (scenes, singletons) in another (e.g., green)
• Plugins in a third (e.g., orange)