user-auth: Add server-induced userData updates #135
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
tbergmueller
force-pushed
the
feature/serverInducedUserDataUpdate
branch
from
facff8c to
f0753d3
Compare
In several occasions server-side logic may want to induce an (enforced) userData update, distributed to all players. Examples: - Moderating: Changing offensive usernames and/or characters - Ownership-based: Loss of ownership of a certain character or characterDescription-Item (includes e.g. NFT-Transfers, when items are represented as NFT) - Game-Events: A group of Users, e.g. the winning team of a challenge, should get awared with a special character or character item.
tbergmueller
force-pushed
the
feature/serverInducedUserDataUpdate
branch
from
f0753d3 to
8469a9c
Compare
MarcusLongmuir
approved these changes
May 20, 2024
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.
In several occasions server-side logic may want to induce an (enforced) userData update, distributed to all players.
Examples:
What kind of change does your PR introduce? (check at least one)