How ungureanueduard/shooting-mush works
Project type and purpose
• This is a full-stack desktop game built on the LibGDX framework.
• It comprises two Gradle modules:
– core: contains the cross-platform game logic
– desktop: contains the platform-specific launcher
File structure
• assets/: all game assets (textures, maps, sounds, fonts, cutscenes)
• core/src/com/mygdx/game/: game code organized by feature
– Game entry points (MyGdxGame, GameScene)
– animations_effects, combat_system, cutscene, entities, game_modes, network, pool_managers, ui_screens, utilities_resources
• desktop/src/com/mygdx/game/DesktopLauncher.java: bootstraps the game on desktop
• build.gradle files: define dependencies and Gradle tasks
Architectural patterns
• Layered game-loop architecture: Input → Update (GameScene, Managers, Entities) → Render → Output
• Feature modules:
– Combat system uses A* pathfinding, bullets, wave management
– Cutscene manager drives scripted events
– Pool managers optimize object reuse for bullets, enemies, particles
– UI screens handle menus, loading, end screens
– Utilities (Assets, Settings, MySQLHelper) abstract resource loading and persistence
Main components and their interactions
a. Platform Layer
– DesktopLauncher: initializes LWJGL backend and hands control to MyGdxGame
b. Core Engine
– MyGdxGame / GameScene: main game loop and scene management
– AssetManager (Assets.java): loads textures, sounds, tile maps
– Input Processor: captures WASD and mouse events
– Update modules:
• CombatSystem (AStarPathfinder, Bullet, Wave)
• EntityManager (enemies, NPCs, turrets)
• CutsceneManager (CutsceneEvent, specific event classes)
• PoolManagers (CharacterBulletsManager, EnemyManager, etc.)
• UI Screens (MainMenuScreen, LoadingScreen, EndGameScreens)
– Rendering modules: Sprite batches, tile-map renderer
– Persistence/Networking: MySQLHelper (score saving), Network.java (multiplayer or coop)
c. Assets & External Services
– Tiled maps (.tmx), fonts, audio files
– External libraries: LibGDX core, LWJGL, Gradle
Architectural patterns and design principles
• Separation of concerns: each feature area (combat, UI, cutscene, pooling) lives in its own package
• Dependency injection via AssetManager and Settings
• Object pooling for performance
• Event-driven cutscene system