Notes |
(0025980)
qoala (reporter)
2014-04-30 08:27
|
Looking through the monster enchantment code, it looks like it might be the fact that the enchantment list is copied over, but not the cache of which enchantments the monster had.
I'll test this and submit a patch when I'm done. |
|
(0025983)
qoala (reporter)
2014-04-30 09:07
|
Patch uploaded.
Since the enchantment cache wasn't copied over, none of the enchantments were being checked during the monster::apply_enchantments() loop for duration updates or available to monster::has_ench(...). (Among other things, the cache allows the update loop to only check pre-existing enchantments when previous steps of the loop can add additional enchantments) On game reload, the cache is generated from the current enchantment list, so that restores behavior.
I checked around the code base, and it appears that everywhere else the enchantments are being copied, the cache is copied as well. |
|
(0026040)
wheals (administrator)
2014-05-04 09:03
|
Seems fine, committed. |
|
(0026069)
Kate (developer)
2014-05-06 15:09
|
Resolving since this was committed. |
|