Proof of concept for cloud high score table which can hold up to 50 names, but only requires one cloud update when a score changes. Basically the ranking is calculated within the program, not in the cloud, and the entries in each cloud variable are fixed-width (in this example 5 entries per cloud variable) so once your name is in the cloud, you hold that cloud position until you drop off the bottom of the ranking table, i.e. someone else takes your place. As the program knows where you are in the cloud list, it only requires one update to update or add your score to the table. The "Sorted List Pos" list tells you the user and score for each position, so to build the list of high scores, simply process this list in order. All I've got to do now is actually use it in a proper project! Also I need to expand this to support "archive entries" (for example in Paint The Maze, I archive people who have completed 100 levels to free up space at the bottom of the table) but that shouldn't be too hard. The makeup of each variable can be changed to suit, e.g. not all projects need to record the level, just the score, and vice versa. The "Ranking" list is an attempt to make sure that if two or more people have the same score, the person who got it first stays above them on the high score list. I've assigned one digit to do this, which means that I can handle up to 9 people getting the same score. If the game is such that this situation could be more common than that, this can be adapted to allow 2 digits for this function, i.e. up to 99 people with the same score. (This might stop working properly if too many gaps appear in the rankings - i.e. people were on the same score but then improved their score, but not a lot I can do about that without resetting everyone else's rank for that score, which defeats the purpose of this project!)
