This repository has been archived by the owner on Nov 18, 2019. It is now read-only.
Persist player ID between refreshes #54
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The player site now caches the ID for the player, and will try to use the cached ID before generating a new one. This ensures that the player will keep their hippo (and their progress) if they refresh their page or close and reopen their browser. This follows up from #52 to drastically reduce the player's ability to grief the game. To reduce the chance of accidental collisions (as described in #19), the player IDs are now generated randomly. We likely don't have to worry about collisions, as there are 264 possible IDs.
Closes #19.