How deety-anh/bombit works
Project type and purpose
• From the file list and the “BomgIt” title in the README, this is a small C++-based 2D arcade/game application (a Bomberman-style game).
• Key files: main.cpp (entry point), Core.* (engine/game loop), GameController.* (state management and input), Object.* (game-object base class), Player.* (player entity), Programs.* (possibly menu or launcher logic), plus an assets folder with sprites and tiles.
File structure
• Top-level C++ source files implement the engine and game logic.
• assets/ holds art assets sorted by type (tiles, bombs, boosts, buttons, player frames).
• No separate “frontend” or “backend”—this is a standalone desktop game.
• No apparent external service integration; the core is the game loop, rendering, input, and asset management.
README for additional insights
• The README is minimal (“# BomgIt”), so rely on file names to infer architecture.
• Entry Point (main.cpp / Programs)
• Game Engine Core (Core.h/.cpp)
• Game Controller (GameController.h/.cpp)
• Entity System (Object.h/.cpp, Player.h/.cpp)
• Asset Manager (loads assets/*.png etc.)
• Rendering Subsystem (graphics API layer)
• Input Subsystem (keyboard/mouse handling)
• Game Loop / Scheduler (timing, update tick)
• Resource Files (assets folder)
b. Relationships and interactions:
• main.cpp invokes Programs → initializes Core.
• Core contains the main game loop: calls Input → GameController → Entity updates → Rendering.
• GameController uses the Entity System to create/destroy Objects and Players.
• Asset Manager is called by Entity constructors or rendering to load textures.
• Input Subsystem feeds events into GameController.
c. Architectural patterns / design principles:
• Separation of concerns: Engine Core vs. Game Logic vs. Entities vs. Rendering vs. Input.
• Component-based or class-hierarchy for in-game objects (Object base class, specialized Player, Bomb, Boosts).
• Single responsibility: asset loading separated from logic; game loop separated from state management.
d. Key technologies and libraries (inferred):
• C++17 or later
• External graphics library (e.g., SDL, SFML, OpenGL)—highlight as “Rendering API”
• Standard filesystem I/O for assets
• Standard containers/memory management for entities
Don’t overthink—capture every distinct component
• Call out the assets folder as its own component.
• If Programs.cpp contains menu logic, represent it as a child of main/initialization.