How jaraorganizacion/game works
Project type and purpose
• This is a 2D Adventure RPG game built with the Godot Engine.
• It uses GDScript for all game logic and includes a custom “Dialogue Manager” plugin in the addons folder.
File structure
• Top-level directories:
• addons/dialogue_manager – custom plugin providing dialogue editing, parsing, compilation, UI panels.
• art – sprite sheets, tilesets, environment and character assets.
• dialogues – source dialogue files (.dialogue) and Godot imports.
• inventory – inventory UI scene, item resources, logic.
• scene – main game scenes (world, NPCs, collectables, menu).
• script – per-object GDScript controllers.
• project.godot – Godot project configuration.
• README.md – high-level description of gameplay features.
README for additional insights
• Open‐world exploration, combat, quests, inventory, pixel art.
• In‐development state; core mechanics in place.
• Technologies: Godot Engine, GDScript.
Main components & interactions
a. Components
• Godot Engine Core – rendering, scene tree, input, physics.
• Scene Manager – loads and switches between scenes (World, Menu, Combat, Inventory UI).
• Game Systems:
– World System (scene/world.tscn + script/world.gd)
– Player Controller (script/player.gd + scene/player.tscn)
– NPC/Enemy System (npc_guns, slime scripts + scenes)
– Collectables System (apple_collectable, stick_collectable)
– Inventory System (inventory/inventory.gd + UI scenes)
– Dialogue System (addons/dialogue_manager plugin + dialogues folder)
– Combat System (integrated in player & NPC controllers)
• Asset Manager – loads art, audio, tilemaps, .tres resources.
• Input Manager – Godot InputMap → player, UI, menu handlers.
• UI Layer – HUD components (progress_bar, errors_panel), inventory panel, dialogue windows
• Resource Files – art/, dialogues/, inventory/items/*.tres
b. Relationships & Data Flow
1. Input Manager captures user input → dispatches to Player Controller or UI Layer
2. Scene Manager organizes active scene, instantiates objects (Player, NPCs, Collectables)
3. Player & NPC Controllers interact → Combat System (health, damage)
4. Collectable & Inventory System: collision events → inventory.add(item) → update UI
5. Dialogue System: when in range of NPC → plugin parses .dialogue → UI shows dialogue → game state updated
6. Asset Manager supplies textures, tilemaps, dialogue scripts
c. Architectural patterns & design principles
• Modular subsystems per game feature (Inventory, Dialogue, Combat)
• Plugin architecture for Dialogue Manager (Godot Editor plugin + runtime compiler)
• Scene tree pattern native to Godot – each object is a Node with attached script
• MVC‐like separation: Scenes (View), GDScript Controllers (Controller/Logic), Resource files (Model)
d. Technologies & frameworks
• Godot Engine (v3.x or v4.x)
• GDScript for all controllers and plugin logic
• Godot Editor Plugins (addons/dialogue_manager)