Bug Fixes and Refactoring
📌 A bug where keys didn't always open doors was fixed by changing a calculation in the `get_detected` method to use `play_speed` instead of simple rounding, ensuring accurate distance checks.
🐛 A minor code logic flaw was corrected by surrounding a sound effect call with an `else` block, ensuring the sound only plays if a parry attempt fails.
🔄 The game over state handling was refactored by creating a centralized `reset_game` method, which handles common state resets (like knockback, attacking, and guarding states) for both 'Retry' and 'Quit' options.
🧹 Status effects such as knockback state, attacking state, guarding state, and writing state were explicitly reset in the `restore_status` method upon restarting the game to ensure clean slate.

Implementing Save/Load System (Player Stats)
💾 Player statistics (level, max life, max mana, experience, coins) are saved using `ObjectOutputStream` to a binary file named `save.dat` via a custom `DataStorage` class implementing the `Serializable` interface.
🔑 Loading player stats involves using `ObjectInputStream` to deserialize the `DataStorage` object from `save.dat`, retrieving values like `DS.level` and restoring them to the player object.
💧 The save functionality is triggered when the player interacts with a water pool, which acts as an in-game save point.
🛑 The load functionality is accessible from the title screen via the "Load Game" option.

Implementing Save/Load System (Inventory, Weapon, and Map Objects)
📦 Inventory saving is handled by separating item data into two lists: one for item names (String) and one for item amounts (Integer), as direct serialization of item *objects* within an entity arraylist was problematic.
🛠️ A crucial utility method, `get_object(itemName)`, uses a `switch` statement to dynamically reconstruct the correct item object from its string name upon loading, though this method is noted as not being highly flexible due to reliance on exact string matching.
🛡️ Current weapon and shield slots are saved and loaded by first implementing getter methods (`get_current_weapon_slot`) within the player class and then updating the player's attack/defense stats post-load.
🗺️ Map objects (like treasure chests) are tracked using a two-dimensional array in `DataStorage` to record their name, world coordinates (`WorldX`, `WorldY`), loot name, and an `opened` status to prevent items from respawning after collection.

Key Points & Insights
➡️ Using `ObjectOutputStream` and `Serializable` objects creates a binary save file (`save.dat`) that is encrypted/obfuscated, making it difficult for users to easily edit game statistics like level or coins.
➡️ The dynamic item loading process relies on string matching via a custom `get_object` method, which is functional but requires meticulous attention to item naming conventions to avoid reference errors.
➡️ Essential world elements like treasure chests must track their `opened` state alongside their identity and location to ensure persistent changes to the game world are maintained across loads.
➡️ Developers should actively seek feedback (as requested by the narrator) for potential improvements, especially regarding flexible object serialization in inventory systems.

📸 Video summarized with SummaryTube.com on Nov 20, 2025, 07:44 UTC