This changes the datastructure in the database to:
Highscores
UserID
ScoreID
Name
Score
ScoreID
Name
Score
UserID
ScoreID
Name
Score
Where the userID is a randomly generated ID unique to that user's phone. The ScoreID is generated in the same way, but one for each submission.
This change is made to prevent one person from occupying more than one slot on the top 10 list, #104. Currently me and Oscar have 9 out of 10 of the top 10 spots, which isn't ideal.
This also means we need at least 10 different devices to submit a highscore before we will fill up the list.
Request also contains small change that means we save the last username submitted and enter that into the input box when submitting highscores.
AxlLind
commented
7 years ago
This changes the datastructure in the database to:
Where the userID is a randomly generated ID unique to that user's phone. The ScoreID is generated in the same way, but one for each submission.
This change is made to prevent one person from occupying more than one slot on the top 10 list, #104. Currently me and Oscar have 9 out of 10 of the top 10 spots, which isn't ideal.
This also means we need at least 10 different devices to submit a highscore before we will fill up the list.
Request also contains small change that means we save the last username submitted and enter that into the input box when submitting highscores.