How hanaaple/techlab_week01_gamejam_7 works
Analyze the File Structure
• Top-Level Directories and Files:
• Assets: Contains subdirectories for Audio and Texture, indicating resource management for sounds and visuals.
• GameObject: Holds various game entities such as Bullet, Monster, and Player, suggesting an object-oriented approach to game entities.
• Manager: Includes managers like AudioManager, GameManager, and UIManager, responsible for handling different aspects of the game.
• Scene: Contains different game scenes (MainGameScene, PresetScene, TitleScene, etc.), managing various states or screens of the game.
• ImGui: Integration of the ImGui library for GUI components.
• Shaders: Contains shader programs (.hlsl files) for rendering.
• UIObject & Weapon: Manage user interface elements and weapon mechanics respectively.
• Math: Likely contains mathematical utilities and vector operations essential for game mechanics.
• GlobalData, BufferCache, InputSystem, URenderer: Handle global game data, rendering buffers, user input, and rendering processes.
• Patterns and Architectural Choices:
• Object-Oriented Design (OOD): Evident from the use of classes and inheritance (e.g., AbstractClass/Singleton.h).
• Manager Pattern: Multiple managers handling specific domains (Audio, Game, UI).
• Scene Management: Different scenes managing various game states.
• Integration with External Libraries: Use of ImGui for UI and possibly DirectX for rendering (imgui_impl_dx11.cpp).
Examine the README for Additional Insights
The README is brief but indicates:
• Project Context: It's part of the Krafton Jungle Game Tech Lab's first-week game jam, developed by Group 7.
• Purpose: While details are minimal, the project likely focuses on creating a functional prototype within a limited timeframe, emphasizing essential game mechanics and features.
a. Identify the Main Components:
• Core Game Engine:
• Rendering Engine (URenderer.cpp): Handles all rendering tasks.
• Input System (InputSystem.cpp): Manages user inputs.
• Math Utilities (Math): Provides mathematical operations and data structures.
• Game Objects:
• Player, Monster, Bullet (GameObject): Represents interactive entities.
• Weapon (Weapon): Manages weapon mechanics and data.
• Managers:
• AudioManager: Handles all audio-related functionalities.
• GameManager: Oversees game states and logic.
• UIManager: Manages user interface elements using ImGui.
• ResourceManager: Manages game assets and resources.
• Scenes (Scene):
• TitleScene, MainGameScene, PresetScene, ResultScene: Different game states/screens.
• Assets:
• Audio (Assets/Audio): Sound effects and music files.
• Textures (Assets/Texture): Visual assets for the game.
• External Libraries:
• ImGui: For GUI components.
• Shaders (Shaders): Shader programs for graphics.
b. Determine Relationships and Interactions:
• GameManager interacts with Scene components to switch between different game states.
• UIManager utilizes ImGui to render user interfaces within different scenes.
• Rendering Engine uses Shaders and Textures from the Assets directory to render game objects.
• InputSystem captures user inputs and communicates with GameManager and Player objects.
• ResourceManager provides necessary assets to other managers and game objects.
• AudioManager plays sounds based on events triggered by GameManager and Game Objects.
c. Highlight Architectural Patterns or Design Principles:
• Singleton Pattern: Likely used in managers (e.g., Singleton.h) to ensure only one instance exists.
• Manager Pattern: Separates responsibilities into different managers for modularity.
• Scene Management: Organized handling of different game states.
• Modular Design: Clear separation between different game components (e.g., GameObjects, Managers).
d. Include Relevant Technologies, Frameworks, or Libraries:
• C++: Primary programming language.
• ImGui: For creating graphical user interfaces.
• DirectX 11: Inferred from imgui_impl_dx11.cpp for rendering.
• HLSL Shaders: Used for graphics rendering.
• External Audio Files: Managed through Assets/Audio.
Elements
• Clear Labels for Each Component:
• Name each component (e.g., GameManager, UIManager, Player, Monster).
• How data moves between components (e.g., InputSystem → GameManager → Player).
Final Recommendations
• Be Detailed and Comprehensive:
• Major components and their interactions are represented.
• Avoid Overcomplication:
• Maintain Consistency: