One database... with many tables. The highscore data is only in one table, but other tables are required to lookup the game name and whether the best score is the highest or the lowest... I think you were both aluding to this
It's a sligtly more difficult problem we're tackling, cos it has to handle multiple sets of highscores for whenever they're reset. Using the same dataset I've also been thinking about an all-time player ranking system, which is more the kind of thing ThundeRumble has done. Two of the ideas I had some time ago are quoted below:
Quote:
|
Originally Posted by Somewhere else Benny
Keep a count of how many 1st positions each player has.
Calculate a skill ranking for each player based on various statistics concerning their scores, positions, dates, etc. (This is starting to sound like a project I would give to a student!  ) |