Additional check in OnPlayerGiveDamage #163
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
|
Seems like the main part of changes aren't fully solved the possible OnPlayerGiveDamage spoofing (as it could be called from vehicle for some non-weapon damage reasons like 49 or 50). |
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.
There are some fixes and other minor corrections. The main is additional check in OnPlayerGiveDamage for player state driver (if player is a driver, he doesn't send this callback and it can help to prevent hacks that spoof OnPlayerGiveDamage this way). Also I've added WC_CONST instead of just 'const' for ApplyAnimation hook. Seems like its needed here too.