How pmassereyes/battlegame-master works
Battle is a JavaFX fighting game. Its documented player journey is character/opponent selection, an active fight with attacks and health changes, then a result screen. The README says the screens share one FXML file and controller; the tree also contains a JavaFX application class, character class, and visual/audio assets. Source excerpts do not reveal runtime wiring, so uncertain connections are dashed and unverified rather than presented as observed calls.
Main entry points: Controller.java Game controller · hello-view.fxml Active combat · HelloApplication.java JavaFX application · Danseur.java Characters
Components 9
Game runtime
- JavaFX application
src/main/java/test/battle/HelloApplication.java - Game controller
src/main/java/test/battle/Controller.java - Characters
src/main/java/test/battle/Danseur.java
Game interface
- Character selection
src/main/resources/test/battle/hello-view.fxml - Active combat
src/main/resources/test/battle/hello-view.fxml - Combat result
src/main/resources/test/battle/hello-view.fxml
Game assets
- Battle visuals
src/main/resources/test/battle/gif battle - Battle music
src/main/resources/test/battle/audio/poppingSong.wav
Other components
- Player
Connections 9
- Player → JavaFX application: starts game
- JavaFX application → Game controller: launches
- Game controller → Character selection: presents selection
- Character selection → Active combat: chooses fighters
README.md - Active combat → Combat result: ends in result
README.md - Game controller → Characters: manages fighters
- Game controller → Active combat: updates fight
- Game controller → Battle visuals: uses visuals
- Game controller → Battle music: plays music