Conversation
The v14 client asks for them itself with MESSENGER_GETREQUESTS right after init (packet 233 arrives immediately after MESSENGERINIT in a trace), so also pushing them from MESSENGERINIT delivered every pending request twice and the console showed duplicates.
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
1 participant
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.
Every pending friend request showed up twice in the console.
MESSENGERINITpushes the pending requests itself (new MESSENGER_GETREQUESTS().handle(player, null)), and the v14 client then asks for them anyway withMESSENGER_GETREQUESTS(233) right after init. This removes the manual push and leaves the client-driven path.Related: #93.