How hdescottes/gdxgame works
Project type and purpose
• This is a 2D RPG game built on the LibGDX framework. It uses a multi‐module Gradle setup with:
• core – the game engine and logic
• desktop – the desktop launcher and platform glue
• Features include map rendering, entity/component system, turn-based battle, inventory, quests, profiles, and UI screens.
File structure
• Top‐level modules:
• core/src/main/java/com/gdx/game – all game subsystems (animation, audio, battle, camera, component, dialog, entities, inventory, manager, map, profile, quest, screen, status)
• desktop – platform launcher (DesktopLauncher)
• Resources in core/src/main/resources: assets (images, maps, JSON scripts), fonts, music, Tiled map files, conversation & quest data.
• Uses Observer pattern heavily (Subject/Observer pairs in audio, battle, inventory, profile, status, dialog, class system).
• Uses a Component‐based entity system (GraphicsComponent, PhysicsComponent, InputComponent).
README for additional insights
• Confirms LibGDX, RPG features, Level Up, Inventory, Battle, Class Tree, automatic saving.
• Mentions resource files produced by Tiled, JSON for quests/conversations, use of AnimationManager, ResourceManager, PreferenceManager.
Detailed capture of essential elements
• Component pattern: Entities composed of multiple components updated by respective subsystems.
• Observer connections for at least one example from each domain (battle, inventory, audio, profile).
• Screen transition flow: Menu → Game → Battle → GameOver → Back to Menu.