[MIRROR] [GBP: NO UPDATE] Fixes a bug where update_inefficiencies() would call update_wounds() and cause gauze to fall off on promotion/demotion of wound [MDB IGNORE] (#23822)

* [GBP: NO UPDATE] Fixes a bug where update_inefficiencies() would call update_wounds() and cause gauze to fall off on promotion/demotion of wound (#78398)

## About The Pull Request

Title.
## Why It's Good For The Game

On some testing on a downstream, I found that demoting a wound to a
lower level via replace_wound caused gauze to fall off. Same thing
happened for promoting. I found the issue lied in the fact
update_inefficiencies always called update_wounds which didnt tell the
proc if a replacement was going on.
## Changelog
🆑
fix: Gauze no longer falls off if a wound is demoted or promoted
/🆑

* [GBP: NO UPDATE] Fixes a bug where update_inefficiencies() would call update_wounds() and cause gauze to fall off on promotion/demotion of wound

---------

Co-authored-by: nikothedude <59709059+nikothedude@users.noreply.github.com>
This commit is contained in:
SkyratBot
2023-09-20 12:59:45 -04:00
committed by GitHub
co-authored by nikothedude
parent a85608ec12
commit 1088153bc4
2 changed files with 4 additions and 4 deletions
+1 -1
View File
@@ -304,7 +304,7 @@
/obj/item/bodypart/proc/update_wounds(replaced = FALSE)
SHOULD_CALL_PARENT(TRUE)
var/dam_mul = 1 //initial(wound_damage_multiplier)
var/dam_mul = 1
// we can (normally) only have one wound per type, but remember there's multiple types (smites like :B:loodless can generate multiple cuts on a limb)
for(var/datum/wound/iter_wound as anything in wounds)