thawkin3 / crossyblock Goto Github PK

@thawkin3 If a user hits F12 they can access the source code for the game. This access can lead to the game's manipulation and can violate a few Test Cases such as score manipulation, removal of obstacles, changing player size so it can avoid collisions and other issues. If there were a way to mitigate source code manipulation it would solve these various Test Cases from being violated.

Failed Test Case: Score should start at 0 (CB-11)
Failed Test Case: Enemies vary in length, but not in width (CB-32)
Failed Test Case: Enemies 'kill' player on contact (CB-33)
Failed Test Case: Enemies vary in speed (CB-34)

If the player 'tabs out' or is forced to by the opening or another application or notification, the game does not pause or stop the players' movement. Which will inevitably lead to a death.

Failed Test Case: Player is not locked into one state i.e. constantly moving in one direction (CB-8)

@thawkin3 When a user scores the same as another high score on the leader board the user either replaces the score tied with or gets placed below that high score. There isn't a definitive way to track whether a score should be replaced above or below in a tie or whether names are placed alphabetically has any impact on above or below other scores.

Failed Test Case: Score Board logs the top 10 scores (CB-13)

If you make the in-game score connected to the distance covered, as opposed to the amount of time the player's block is alive, then you could potentially fix the alt-tabbing bug, and provide a better measure of progress. This could cause some extensive rewrites to the code though, but this is just my team's suggestion.