How marambfa/acl-isn-2025-bug_busters works
Project type and purpose
• This is a standalone, desktop Java game (“Jeu de Labyrinthe”) built with Maven.
• It comprises a small game engine, a Swing/JavaFX (or AWT) based UI, and a set of domain‐model entities representing heroes, monsters, keys, treasures, etc.
File structure
• Top level:
• pom.xml – Maven build descriptor
• src/main/java – production code
◦ com/example/App.java – generic entrypoint stub/test
◦ main – game launcher, window, engine classes
◦ entity – domain model (Heros, Monstre, Weapon, etc.)
◦ simple – utility/value classes (Position, Difficulty)
• src/main/resources/images – static assets
• src/test/java – unit tests
• No microservices or external servers—everything runs in one JVM process.
• No external dependencies beyond JDK17 and possibly a GUI toolkit.
README
• Build: mvn clean compile
• Run: mvn exec:java
• Target environment: Java 17, Eclipse IDE
Main components
a. Game Launcher
– Main.java initializes the application.
b. Game Engine / Core Loop
– Labyrinthe.java orchestrates tile setup, entity placement, game ticks.
c. UI Layer
– FenetreLabyrinthe.java renders the maze, sprites, handles user input.
d. Domain Model
– Entities: Heros, Monstre, Ghost, Zombie, Cle, Tresor, Weapon (+ WeaponType, PointsDeVie).
e. Utilities
– simple.Position, simple.Difficulty for grid coordinates and difficulty settings.
f. Resources
– images folder providing sprite assets.
g. Build & Execution
– Maven plugin → compiler → exec:java
Relationships & interactions
• Main → invokes Game Engine’s initialization
• Game Engine ↔ Domain Model (creates and updates entity states)
• Game Engine → UI Layer (pushes updated state each tick)
• UI Layer → User Input → Game Engine (commands to move, pick up keys)
• Both Game Engine & UI → read from resources/images
• Maven → compiles code + packages resources → exec plugin runs Main
Architectural patterns & principles
• Clear separation of concerns:
• Launcher (startup)
• Engine (game logic loop)
• Domain (state containers)
• UI (view & controller)
• Utilities (shared value types)
• MVC‐like flow: Model (entities) → View (FenetreLabyrinthe) ← Controller (keyboard handlers inside UI or Engine)
• Resource isolation: image assets separate from code
Essential elements
• Clear component names
• Build & run flow via Maven