When you look at the scores you can see a list of the top 5 runs on a level. Each has the option to replay the ghost if it was recorded.
Do we want to download all the 5 ghosts when we show the scores or only adhoc when requested? At the moment there is no score caching, but this could also be implemented.
What is the directory structure for ghosts?
When recording the player during runs, the ghosts are all stored separately from the levels. Only one ghost is stored per level (the most recent run) which is either submitted on completion, or overridden if the player starts a new run.
If we are going to download multiple ghosts for a level when scores are viewed, they should probably be stored with the level data and the naming should be the creator id (which will only show once per leaderboard).
Questions
How should we store ghosts locally?
When you look at the scores you can see a list of the top 5 runs on a level. Each has the option to replay the ghost if it was recorded.
Do we want to download all the 5 ghosts when we show the scores or only adhoc when requested? At the moment there is no score caching, but this could also be implemented.
What is the directory structure for ghosts?
When recording the player during runs, the ghosts are all stored separately from the levels. Only one ghost is stored per level (the most recent run) which is either submitted on completion, or overridden if the player starts a new run.
If we are going to download multiple ghosts for a level when scores are viewed, they should probably be stored with the level data and the naming should be the creator id (which will only show once per leaderboard).