How nkdkhtl/chessgame works
Project type and purpose
• Type: Standalone Java desktop application (built with Java Swing).
• Purpose: Play chess locally—supports two‐player mode, AI opponent (Easy/Hard), save/load games, multiple themes and sounds.
High‑level components
a. Presentation Layer (UI)
– Packages: src/panels (GameMenuPanel, GameModePanel, GameOverPanel, PromotionPanel, SettingsPanel, TimerPanel)
– Utils for UI: src/utils (BackgroundPanel, StyledButton, ScaleImage, ThemeManager)
– Entry point: src/Main.java → initializes GameLauncher
b. Core Game Logic
– src/GameLauncher (Board, Movements, CheckFinder, MouseInput, Type, GameLauncher.java)
– src/pieces (Piece hierarchy: King, Queen, Rook, Bishop, Knight, Pawn)
c. AI / Bot Engine
– src/bot (Bot, EasyBot, HardBot)
– src/bot/engine (SearchEngine, Evaluator and subtypes: OpeningEvaluator, MiddlegameEvaluator, EndgameEvaluator, GamePhaseEvaluator)
d. Persistence & Settings
– src/utils/SettingsManager (load/save game state)
– settings.xml (global configuration)
e. Resource Management
– src/utils/SoundManager
f. Utilities
– ChessTimer, ThemeManager, SoundManager
Relationships & Interactions
1. User clicks UI component (e.g., a square):
UI Panel → MouseInput → GameLauncher → Movements → Board → Piece → CheckFinder
2. Board state change triggers UI refresh:
Board → panels (repaint)
3. AI move request:
GameLauncher (on bot mode) → Bot (EasyBot or HardBot) → SearchEngine → Evaluators → returns Move → GameLauncher applies via Movements → Board
4. Save/Load:
SettingsManager ↔ GameLauncher/Board (serializes state to settings.xml)
5. Resource loading:
ThemeManager, SoundManager, ScaleImage load resources from res/ and bin/
Architectural patterns / design principles
– Layered architecture (Presentation / Domain / Persistence / Utilities)
– MVC‑like separation: UI panels (View), GameLauncher/Movements (Controller), Board/Piece (Model)
– Strategy pattern in Evaluator (different evaluation strategies for game phases)
– Factory or Polymorphism in Bot selection (EasyBot vs. HardBot)
– Single responsibility in utility classes (ThemeManager solely manages themes, SoundManager solely handles audio)
Essential elements to capture
– Presentation: panels, ThemeManager, SoundManager
– Controller: GameLauncher, MouseInput, Movements, CheckFinder
– Domain: Board, Piece hierarchy
– AI: Bot, EasyBot, HardBot, SearchEngine, Evaluators
– Persistence: SettingsManager, settings.xml
– Resources: res/, bin/
– Entry point: Main.java