auth: v2 ConnectResult #2471
Closed
auth: v2 ConnectResult #2471
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
buck54321
force-pushed
the
more-tier-data
branch
from
48a3e19 to
96e3c51
Compare
|
Replaced by #2501 |
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.
Fully resolves #2461, though we're in a precarious state if the server is < v2 connect result (see notes here and in #2460).
Add a
TierReportV2field toConnectResult,TierChangedNotification, andPostBondResult. TheTierReportV2 account.TierReportfield deprecates theTier int64andLegacyFeePaid boolfields in these responses, though the fields are still populated (V0PURGE).The
account.TierReportincludes information about bonus tiers and revoked tiers, allowing the client to maintain a their bonded tier accurately.