How uzi-belfayez/acl_project works
Project type and purpose
• This is a standalone Java 2D desktop game (“Balade dans un labyrinthe”) built with Maven.
• The player navigates a maze, collects keys, battles monsters and ghosts, and advances through levels.
File structure
• Top-level Maven project (pom.xml) with standard src/main/java, src/main/resources, and src/test/java.
• main package holds core game systems:
• GamePanel, Main (entry point)
• AssetSetter (loads entities & objects onto the map)
• CollisionChecker (detects and resolves collisions)
• EventHandler & KeyHandler (input processing)
• UI (draws HUD)
• UtilityTool (generic helpers)
• entity package defines in-game actors: Player, Monstre, Ghost, Fireball, plus base Entity.
• object package holds collectible or interactive items (keys, doors, boots, chests, etc.).
• tile package defines Tile and TileManager (loads map, tiles).
• resources contains images and map definitions.
• JUnit tests in src/test/java verify core entities’ behavior.
README
• Confirms game objectives and controls.
• Shows build & run via Maven.
a. Main components
• Launcher: Main.java
• Game Engine/Core Loop: GamePanel
• Input Layer: KeyHandler → EventHandler
• Asset Management: AssetSetter + UtilityTool
• Game World Representation: TileManager + map files
• Actors & Items: entity classes + SuperObject & its subclasses
• Collision System: CollisionChecker
• Rendering/UI: UI + GamePanel.paintComponent()
• Persistence/Resources: images, map text files
• Build & Test: Maven (pom.xml), JUnit tests
b. Relationships & interactions
• Main initializes GamePanel & window.
• GamePanel runs the loop:
• Poll input → KeyHandler → EventHandler → updates entity states
• AssetSetter loads entities/objects once at level start
• TileManager holds static map collision & rendering grid
• CollisionChecker invoked each tick to resolve overlaps
• GamePanel invokes UI to overlay HUD on rendered scene
• All modules read from src/main/resources.
• Tests target entity behaviors in isolation.
c. Architectural patterns & design principles
• Game Loop pattern
• Separation of concerns: input, update, collision, rendering
• Factory/Setter pattern for assets (AssetSetter)
• Manager classes (TileManager, CollisionChecker) encapsulate related logic
d. Key technologies & libraries
• Java SE (AWT/Swing or Java2D) for rendering & input
• Maven for build, dependency management, packaging
• JUnit for unit tests