Fixed ServerSpoof sending incorrect client brand #4480
Closed
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 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.
Type of change
Description
Fixes a bug where turning on brand spoofing in server spoof does not spoof the brand.
Related issues
Fixes issue: #2404
How Has This Been Tested?
Tested server brand spoofing using Vulcan anti cheat.
Warning: I do not have access to Wraith anti cheat so I could not test the server spoof with that. Vulcan does not seem to detect the fact that branding is being spoofed. This is Vulcan though so who can say how good this test is...
Checklist: