Group 3 — Fixing Changes and Code Logic

29/08/26 — Adding Input Checking
I worked on making the program more reliable by adding input checking. Before this, entering something unexpected could cause errors or stop the program. I added checks so invalid inputs could be handled and the player could try again.

03/09/26 — Preventing Repeated Items
While testing the random item system, I noticed that the same item could appear repeatedly. I changed the generation logic so the program checks previously selected items before generating a new one. This helped make the rounds more varied.

05/09/26 — Fixing Ability Logic
As I added more abilities, I had to make sure the program was correctly tracking their uses and effects. I worked on the logic for reducing charges when an ability was used and making sure the correct effect was applied without accidentally generating another round.

07/09/26 — Fixing Percentage Calculations
I worked on the percentage ability and found that the calculation needed to work regardless of which item had the higher price. I used an absolute difference so the percentage could be calculated correctly in either direction.

07/09/26 — Adding Ability Regeneration Logic
I added logic for abilities that can regenerate after a certain number of rounds. This required keeping track of the player’s progress and checking when the required number of rounds had passed before restoring the charges.

09/09/26 — Improving Code Feedback
I worked on the feedback given by the program after different actions. Instead of only changing variables in the background, the program now tells the player what happened when an ability is used or when an important gameplay event occurs.

16/09/26 — Fixing WordL Logic
I continued testing the WordL checking system and found issues with how guesses were being handled. I adjusted the validation and feedback logic so that letters were checked against the target word more consistently.

17/09/26 — Cleaning Up the Code
I went through the code after the recent changes and checked for remaining issues. I also looked at the formatting and comments because some lines had become too long. Cleaning this up made the code easier to read and maintain while continuing to follow the expected coding standards.