jvondermarck/dinosaur-exploder

👉 Please confirm the following I agree to follow the Code of Conduct that this project adheres to. I checked the current issues for duplicate features. 🤔 Is your proposal related to a problem? yes 😍 Describe the solution you'd like In the game the full screen option does not works (its excluded). Adding a full screen option. And a window resizing option. And even what is present does not fits the screen. See the video for reference --> Screen.Recording.2026-10-11.194846.mp4

👉 Please confirm the following I agree to follow the Code of Conduct that this project adheres to. I checked the current issues for duplicate features. 🤔 Is your proposal related to a problem? Enemies' speed is pretty slow while asteroids pretty fast. 😍 Describe the solution you'd like Let's change asteroids speed for the Easy mode Tiny hint: would need to make a change for example in this file GameMode, to add a new field for asteroid speed. 👍️ Describe alternatives you've considered No response ✍ Additional context No response

👉 Please confirm the following I agree to follow the Code of Conduct that this project adheres to. I checked the current issues for duplicate features. 🤔 Is your proposal related to a problem? ScoreComponent, CollectedCoinsComponent, and SettingsProvider all read/write hardcoded relative filenames directly (highScore.ser, totalCoins.ser, settings.properties — the first two also duplicated as literal strings in FileDataProvider rather than referencing GameConstants). Because the path isn't injectable, tests that exercise these classes run against whatever save files happen to sit in the working directory — there's no way to isolate a test in a temp directory, which blocks writing real regression tests for save/coin persistence and settings load/save behavior (this came up while working on #488/#493). By contrast, ShipUnlockChecker/WeaponUnlockChecker already take a DataProvider via constructor injection, and tests fake it cleanly (see SelectionTest/UnlockBoundaryTest) —

👉 Please confirm the following I agree to follow the Code of Conduct that this project adheres to. I checked the current issues for duplicate features. 🤔 Is your proposal related to a problem? Several recent bugs show that the current test suite does not protect some important game-state invariants: #478: CollisionHandlerTest can overwrite the player's high scores and total coins. #479: paused wall-clock time was included in TIME PLAYED. #480: toggling mute from a stale menu instance can restore an older language. #481: repairing malformed settings can return null to the original caller. The suite currently passes while these behaviors remain possible. The missing coverage is not about a percentage target: persistence, game time and settings updates are coupled directly to production files, FXGL state or long-lived UI snapshots, so the relevant behavior cannot be tested deterministically. This Feature should protect the business rules exposed by those bugs without replacing

👉 Please confirm the following I agree to follow the Code of Conduct that this project adheres to. I checked the current issues and pull requests for duplicate bugs. ❌ Current Behavior Running CollisionHandlerTest from the repository root overwrites the player's real highScore.ser and totalCoins.ser files even though all 8 tests pass. In a controlled reproduction, the saved state changed from Normal high score 20, Expert high score 2, and 29 coins to a high score of 5 and 15 coins. The files' SHA-256 hashes changed as well. ✅ Expected Behavior Automated tests should use isolated temporary persistence and must not modify player save data in the working directory. 🚩 Steps To Reproduce On the unmodified main baseline, create or retain save data with a high score greater than 5 and more than 15 coins. Back up or hash highScore.ser and totalCoins.ser. Run mvn -B -Dtest=CollisionHandlerTest test. Confirm that the test reports 8 tests passing. Compare the save files or launch t