copy_from
makes zombifies_into
impossible to remove via delete
#62019
Labels
<Bug>
This needs to be fixed
Monsters
Monsters both friendly and unfriendly.
(S2 - Confirmed)
Bug that's been confirmed to exist
Describe the bug
In #61668 I made the smallest dogs not zombify. Or, well, I thought I did. The code is there, it should work. It was such a simple change I didn't even bother to test it. The problem is that now it turns out my way to remove the
zombifies_into
field didn't work. This was brought to light in #62008 where it turned out thatcopy_from
andzombifies_into
have a deep romance that cannot be broken by conventional means. Usingdelete
will simply be ignored, while supposedly (I did not test that myself, however, that is what I was told is the case) settingzombifies_into
tomon_null
does stop the zombification while not removing the warning icon on a corpse.Steps to reproduce
zombifies_into
should be properly removedExpected behavior
delete
should not randomly lose its expected functionality on just one random field. I'd hazard a guess it doing just that isn't expected considering #61668 was approved and merged.Screenshots
A beautiful corpse of a dachshund with a revival warning icon despite the code implying the monster shouldn't zombify.
Versions and configuration
Dark Days Ahead [dda],
Disable NPC Needs [no_npc_food],
No Fungal Growth [no_fungal_growth],
Bionic Professions [package_bionic_professions],
Tamable Wildlife [Tamable_Wildlife]
]
Additional context
Didn't test it but I think it'd be worthwhile to take a look at what happens whether a monster using
copy_from
from some other monster that zombifies has azombifies_into
defined but aimed at a different zombie. Which zombie will it revive as?The text was updated successfully, but these errors were encountered: