How l1tesg/dirty-road-godot works
1. Repository shape
- This repo is a two-part project: a Godot game under juego/ and a separate Astro static website under pagina-web/.
- There is also a small documentos/ area for supporting docs. The architecture is mostly client-side/offline; no backend or database layer is visible.
2. Game entry and runtime boundary
- The game is rooted in juego/project.godot, which defines the Godot runtime configuration.
- The likely startup flow is menu_ui/MAIN.tscn → menu scripts → gameplay scenes such as mapas/level_1.tscn or sewer/sewer_nivel.tscn.
- Scene transitions are the main composition mechanism: Godot scenes and scripts orchestrate the game instead of a central application server.
3. Menu and front-end game flow
- juego/menu_ui/ holds the main menu and save/load-style UI flow:
- main.gd / MAIN.tscn as the top-level menu entry.
- menus/menu_inicio.* for the start menu.
- partidas/selector_partida.* and partidas/partida.* for save-slot or profile selection.
- This is a clear boundary between presentation/navigation and actual gameplay scenes.
4. Gameplay scene layer
- juego/mapas/ and juego/sewer/ contain world scenes and their level logic:
- mapas/level_1.tscn with level_1.gd is the main level implementation.
- mapas/game/prueba_level1.tscn appears to be a test or variant scene.
- sewer/sewer_nivel.tscn is another standalone level/environment.
- These scenes are the integration points where level geometry, enemies, props, and player nodes are assembled.
5. Player subsystem
- The player is isolated in juego/player/leroy.tscn with leroy.gd.
- This likely owns movement, combat/action handling, animation control, and interaction with environment objects.
- The player subsystem feeds events into the level world: collecting items, triggering doors, interacting with save points, and reacting to hazards.
6. World interaction/content model
- The asset catalog strongly suggests the world is built from interactable content such as:
- Doors, keys, ladders, save points, usable items, traps, props, and enemies.
- These are not separate services; they are content-driven scene objects imported into level scenes.
- The gameplay loop appears to be exploration plus interaction with environment triggers and enemy encounters.
7. Art/content pipeline
- Most of the repository is asset-heavy and organized around Aseprite source files:
- assets/…/*.aseprite for sprites and animation frames.
- assets/music/*.mp3 for audio.
- assets/fonts/, assets/images/, and assets/gif/ for supplemental media.
- This means the game’s visual/content pipeline is asset-first: art is authored externally, then imported into Godot scenes/resources.
8. UI and presentation assets
- UI is split between scene logic and art resources:
- assets/User Interface/ and assets/themes/ hold HUD and styling assets.
- assets/mobile-controls-1.0/ provides mobile on-screen control art.
- addons/phantom_camera/panel and related theme files support editor-facing UI for the addon.
- In diagram terms, UI is a separate presentation layer on top of gameplay scenes, with theme resources applied by Godot.
9. Camera and editor addon boundary
- juego/addons/phantom_camera/ is an embedded third-party plugin, not core game code.
- It includes runtime camera classes plus editor plugins, gizmos, and example scenes for 2D/3D camera behaviors.
- Architectural role: it acts as an external subsystem used to manage camera following, framing, noise, tweening, and editor tooling, while remaining decoupled from the game’s own gameplay scripts.
10. Testing and sample scenes
- juego/nodes/ contains generic scenes such as mapa.tscn and test_Movimiento_jugador.tscn, which look like reusable test harnesses or prototyping scenes.
- The addons/phantom_camera/examples/ tree is also present, showing the repo carries vendor examples alongside the actual game.
- These areas are useful for development but should be treated as supporting/prototyping boundaries, not primary gameplay flow.
11. Web presence
- pagina-web/ is a separate Astro project with its own package.json, astro.config.mjs, and src/pages/index.astro.
- This is a static site boundary, likely used for project presentation or documentation rather than game runtime.
- It does not appear to share runtime code with the Godot game; it is an independent deployment unit.
12. Documentation and asset versioning
- documentos/APA.docx and assets/UPDATES/… indicate the repo also stores planning/reference material and multiple asset-update drops.
- The duplicated asset trees under assets/ and assets/Another Metroidvania Asset Pack Vol. 1 ver. 1.7/ suggest imported third-party art packs plus evolving revisions.
- For an architecture diagram, this is important as a content-management boundary: the game consumes a large prebuilt asset library rather than generating content procedurally.
13. Overall data flow
- The main flow is: menu selection → level scene load → player/world interaction → UI feedback and scene progression.
- Within gameplay, Godot scenes bind together scripted behavior and imported resources, while the camera addon and UI themes shape presentation.
- There is no visible remote service or persistence backend; state is likely maintained locally by the Godot game and its scene/resource system.
Main entry points: level_1.tscn Level 1 · MAIN.tscn Main menu · leroy.tscn Player · plugin.cfg Camera addon
Components 19
Godot game
Core game runtime, scenes, scripts, and embedded addon
- Project · Godot project configuration and runtime entry boundary
juego/project.godot - Main menu · Top-level menu scene and navigation script
juego/menu_ui/MAIN.tscn - Start menu · Start screen logic and scene
juego/menu_ui/menus/menu_inicio.tscn - Save select · Save-slot/profile selection screens
juego/menu_ui/partidas/selector_partida.tscn - Level 1 · Primary gameplay level and its script boundary
juego/mapas/level_1.tscn - Sewer level · Standalone sewer environment scene
juego/sewer/sewer_nivel.tscn - Test level · Reusable test or prototype scene for level work
juego/mapas/game/prueba_level1.tscn - Player · Player scene and movement/combat script boundary
juego/player/leroy.tscn - World content · Doors, keys, ladders, save points, props, traps, and interactables
juego/assets/Props/chests/aseprite files/brown_chest_opening.aseprite - Enemies · Hostile character and boss asset families used by levels
juego/assets/Enemies/Zombie/going left animations/aseprite files/zombie_attack_left_anim.aseprite - UI assets · HUD and theme resources for in-game presentation
juego/assets/User Interface/char hud/health bar/aseprite files/health_bar.aseprite - Audio · Imported music used by the game
juego/assets/music/Glint_of_the_Falls.mp3 - Art pipeline · Large imported Aseprite source pack and update drops feeding Godot scenes
juego/assets/Another Metroidvania Asset Pack Vol. 1 ver. 1.7/read me (or not).txt - Camera addon · Third-party Phantom Camera plugin boundary used for following/framing
juego/addons/phantom_camera/plugin.cfg - Camera runtime · Core camera manager and camera host classes
juego/addons/phantom_camera/scripts/phantom_camera/phantom_camera_2d.gd - Editor tools · Inspector, panel, and gizmo tooling for the camera addon
juego/addons/phantom_camera/panel/editor.tscn - Examples · Vendor example scenes and sample scripts shipped with the addon
juego/addons/phantom_camera/examples/example_scenes/2D/2d_example_scene.tscn
Website
Independent Astro static site
- Website · Independent static website project
pagina-web/src/pages/index.astro
Connections 21
- Project → Main menu: launches · Godot runtime starts in the main menu flow
- Main menu → Start menu: navigates to · Menu scene hands off to the start menu
- Main menu → Save select: opens · Menu flow leads into save/profile selection
- Main menu → Level 1: starts · Menu can transition directly into gameplay
- Save select → Level 1: loads · Selected slot enters the main level
- Level 1 → Player: spawns · Gameplay level composes the player scene
- Level 1 → World content: assembles · Level scene places doors, keys, ladders, props, traps, and save points
- Level 1 → Enemies: populates · Level scene includes hostile encounters
- Level 1 → UI assets: overlays · Gameplay renders HUD and theme resources
- Level 1 → Audio: plays · Level can attach music and sound assets
- Sewer level → World content: assembles · Sewer scene uses the same content-driven object model
- Sewer level → Enemies: populates · Sewer environment includes combatants and hazards
- Player → World content: interacts with · Player actions trigger doors, keys, save points, and usable items
- Player → Enemies: engages · Player movement and combat respond to enemy encounters
- Art pipeline → Level 1: feeds · Imported art packs are turned into level-ready content
- Art pipeline → Player: feeds · Character animations and variants support the player scene
- Camera addon → Camera runtime: contains · Addon runtime classes and manager logic
- Camera addon → Editor tools: contains · Addon editor panels and gizmos
- Camera addon → Examples: ships · Example scenes demonstrate addon behavior
- Camera runtime → Level 1: follows · Gameplay levels use the camera system for framing
- Website → Docs: complements · Static website sits beside repository documentation