[MP] Add prediction for disabled/forced buttons #463
Conversation
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
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.
This PR networks each player's disabled/forced buttons and makes clientside prediction commands account for them. This fixes prediction errors when attempting to use a disabled button or not pressing a forced button. For example, prior to this PR, if the player attempted to fire their weapon while
IN_ATTACKis disabled, their viewmodel and bullet FX would act as if the weapon was fired.The disabled/forced buttons feature is used by
player_speedmod,trigger_playermovement, and some VScript functions which allow their direct control.PR Checklist
developbranch OR targets another branch with a specific goal in mind