Posting this here because I don’t have access to the war within
I hope to see an issue addressed here. Some of the newer encounters seem to switch NPC’s which means they lose their debuffs (like spark and touch). For example, Morchie. If you start burning Morchie after you’ve found the right one you will lose your radiant spark (and touch), She turns into a dragon for a moment and then turns back into herself again … but she’s not the same “herself” so she no longer has the spark debuff.
To me this is one of the only truly frustrating aspects of playing Arcane. I like the complexity overall, but the dungeons are built to work against spark so while most everyone else gets to do their rotation an Arcane mage has to wait for this mechanic to happen. It also happens on the blight of galakrond. If you don’t get spark in at the very start of the phase then you lose your damage to something that isn’t gameplay but rather what seems like coding/programming choices to swap out NPCs rather than morph that one in to the next phase. I think the blight of galakrond boss is 6 separate NPC’s essentially. I think other classes that have debuffs will appreciate this, too!
2 Likes
How about we just remove it and buff overall damage?
3 Likes
As far as I can recall this has always been the case and applies to all DoTs or debuffs not just RS and TotM, though of course it’s a lot more impactful for us since so much of our damage is tied to that brief window, but that’s where knowing a fight well enough to know when to hold your cooldowns comes into play. Also it is a technical limitation rather than an intentional mechanic. If it’s a coding issue as we all suspect it’s very unlikely that they would ever fix it.
I don’t think this is intended to be a game mechanic, it is an artifact of implementation. There are plenty of interesting game mechanics that were intentional and can amp your damage if you know them. This doesn’t seem like that at all.
As a person who knows these fights well enough to play around this issue I still find it unsatisfying.
“It’s always been that way” is not a compelling argument IMO
I literally said that:
I completely agree. I was merely pointing out that because it’s always been the case and because it’s more than likely to be a coding issue it means that they either can’t or won’t fix it. And let’s be honest, it’s a fairly minor inconvenience that doesn’t occur very often because very few mobs or bosses behave this way.