Simon says doesn't end after an incorrect input

[TotallyOriginalUsername]

#51 introduced a new change to how an incorrect input gets handled, which causes the game to not end after getting an incorrect input anymore. This makes it not accurate to how the game was supposed to work

[kasper201]

This is not actually the case. The change in minigame #51 allows for the minigame to be played twice after which the game will still end. This means that a player can either finish the minigame by playing the entire sequence correctly once or try 3 times after which the game will end and the highest score the player achieved should be given.

There however are 2 known issues related to this pr which were looked over. These issuers are:

• Score gets reset after an incorrect input instead of storing the highest score.
• define "maxAttempts" defines a maximum of 2 attempts but the minigame gives the player 3 attempts.

[TotallyOriginalUsername]

That's still an undocumented change, and not mentioned in the PR which changed how this minigame works.
Because of the original code and UML only saying this game is meant to be played once I'm calling this a bug, as allowing the game to be played multiple times is not how the game is meant to be played.
A minor PR which was supposed to add sound to a minigame introducing two new issues is also a bad problem and why we might need stricter testing of minigames.

You also said they are known issues, but I don't see them in the issues list right now.