Add ability to make client-side vehicles damageable #4600
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
qaisjp
requested changes
Jan 6, 2026
qaisjp
approved these changes
Jan 7, 2026
Member
qaisjp
left a comment
qaisjp
left a comment
There was a problem hiding this comment.
Thanks! Sorry for the delay with the review. Gonna sort out my GitHub notifications...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 makes it possible to mark a client-side vehicle to be damageable. By default client-side vehicles cannot receive damage, this PR does not change that default behavior.
When false is passed to SetVehicleDamageProof for a local vehicle, it will now become damageable.
PREVIOUS: #4411