Seems that pandemic is no longer working for any classes/removed?
Bugged. Hopefully they fix it ASAP; this makes SPriest literally unplayable in its current state.
1 Like
How on earth did they break THAT?
4 Likes
Hilarious how they tenuously say locks came out unscathed by this bug.
2 Likes
i really don’t know what intern was digging around messing with the pandemic code but jfc
this better be a bug and not a feature
Probably has something to do with BM not being “viable” if forum trends persist.
Might have something to do with Pandemic originally being a Lock ability (and possibly still is) whereas the other users of pandemic all benefited when the base mechanics where changed to incorporate it within the design.
That’s what I read as well, but given after this much time after said change. I would have hoped code parity would have been reached in spell backend functionality.
But I would guess they don’t even have 100% tested spell templates that they then copy paste (to then modify later on) for classes. Just iteratively working on the old stuff.
Like as an example there is no way why say for instance they couldn’t make a template for an @cursor functioning spell like blizzard, flamestrike, DnD, etc. It would be really really smart to have a @cursor template spell with all the spell fields being default and then tweak that base template as needed depending on the intended functionality. But that would ensure that you have at least a stable base to work on. That way in the future you can just tweak the template (for some future change) and it will be properly applied to all spells using said template.
Literal spaghetti code.
1 Like