Alysha Hawkeye Posted April 3, 2017 Share Posted April 3, 2017 I play a Warlock with Dragoncall build. This build looks cool for AoE trash mobs thanks to wider radius of Dragoncall compared to Helix. However, in reality, it's actually not. When you current target dies during your Dragoncall casting (when the dragons are twirling around), it won't fire off and goes into cooldown. This messes up your rotation and makes your Dragoncall cooldown go longer than necessary, and waste your AoE potential. I think the problem here is that Dragoncall is a delayed spell, both instant cast and hard cast. Perhaps the cooldown should not be active if the spell gets cancelled when target dies. Link to comment Share on other sites More sharing options...
Quantum Posted April 3, 2017 Share Posted April 3, 2017 I feel they could just make the dragoncalls (in which the target has died) still go to the last target's location and explode, or just make it change its target to whatever you're currently targeting instead. Link to comment Share on other sites More sharing options...
SadFace Posted April 3, 2017 Share Posted April 3, 2017 8 hours ago, Quantum said: I feel they could just make the dragoncalls (in which the target has died) still go to the last target's location and explode i always felt like it should work like this and was so frustrating to see the dragon to disappear mid air. One of the reasons why i rarely used ice build. Link to comment Share on other sites More sharing options...
Pkmdz Posted April 3, 2017 Share Posted April 3, 2017 Reasons I use shadow :( Link to comment Share on other sites More sharing options...
Kisagii Posted April 3, 2017 Share Posted April 3, 2017 Happens to me but I've never had a problem since I can always get another cast since I never leech on mobs. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.