Overview

This page records my individual Sprint 4 contributions to gameplay and regression prevention in the project. The work covers a loot-size adjustment, a sliding-stamina bug fix, a guard against health regeneration after death, and bribe/gameplay regression-test corrections.

Diagram accuracy:

The flowcharts describe the behaviour in the task summary. The UML diagrams are marked conceptual where explanatory class relationships or method calls are shown.

Gold Coin Size Fix

Problem: The gold coin appeared too large in the game world.

Change: Updated the relevant loot entity factory code to reduce the coin's size. Pull request: #424 — Gold coin size and sliding stamina fixes The change adjusts the coin's in-world presentation without changing its role as loot.

Sliding Stamina Fix

Problem: Pressing Left Shift while the player was stationary consumed stamina even though no useful slide could occur.

Change: Updated the sliding logic in PlayerActions so a stationary slide attempt does not consume stamina. For a moving player, the intended behaviour checks stamina availability before starting the slide. Pull request: #424

Figure 1. Behavioural flowchart for stationary and moving slide attempts.

Figure 2. Conceptual sequence diagram. The stamina participant is labelled generically

Health Regeneration After Death

Problem: Health regeneration continued after the player had died.

Change: Updated PlayerRegenComponent to stop regeneration when the player is dead, and added a regression test for this behaviour.

Figure 3. The dead-player path skips healing. The regeneration-timing branch is a behavioural explanation.

Figure 4. Conceptual relationship diagram.

Bribe Regression Test

Contribution: Corrected a regression test related to the bribe functionality so that the test better reflects the expected behaviour. Pull request: #479

This contributes to regression protection by keeping the bribe behaviour covered by an automated check.

Gameplay and Regression Testing

I also contributed gameplay and regression tests intended to verify expected behaviour and help prevent existing bugs from returning. Pull request: #455

Figure 5. High-level verification workflow for the listed fixes.

Figure 6