Repository navigation
feat(mastery): per-player progress with provenance - #79
Merged
Merged
Conversation
The inventory cache holds one account and records no observation time, so a second account on the same machine overwrote the first and the overview could not say how fresh its ranks were. Affinity now lives in its own cache keyed by the EE.log player name, stamped with the tick that applied each blob. A blob confirms only the player it was captured under: one queued across a switch, or matching bytes from before it, confirms nobody.
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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 inventory cache holds one account and records no observation time, so a second account on the same machine overwrote the first and the overview could not say how fresh its ranks were.
Affinity now lives in its own cache keyed by the EE.log player name, stamped with the tick that applied each blob. A blob confirms only the player it was captured under: one queued across a switch, or matching bytes from before it, confirms nobody.