Brute Damage Causing Burns Bugfix #36482
Merged
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.
What this does
Fixes... uhh he never made the bug report. This PR fixes a rare albeit hilarious bug where sometimes when taking brute damage, you would actually take burn damage somehow. This was caused by the code that expands existing wounds not checking for the appropriate damage type.
Example: Remember that door you failed to hack roundstart? That burn wound on your hand, despite being cured like 30 minutes ago, has remained on you in the form of a grizzly burn scar with 0 damage! Later, when someone hits you in that same hand with a 10 melee damage shotgun, the damage initially attempts to expand an existing wound before creating its own. Hey, look, it's an old burn damage burn scar! Riiiip, 10 burn damage.
Why it's good
Because it removes a funny bug, it's not. But I guess consistency is good. If you get hit with brute damage, you expect to take brute damage.
How it was tested
me realizing how terrible our wound code is
(Tested via attacking self with various medical tools and lighters while using VV alongside debug messages to confirm status of wounds inflicted)
Changelog
馃啈