Something is going funny with Steal Time

aganway

I don't know what is happening, but I'm using Steal Time on tab and sometimes it goes onto permanent cooldown, well the system thinks it is on cooldown. It will work fine for ages then suddenly it will not trigger properly - I get the first 1 second of the animation and the full sound, but it stops after that 1 sec and the timer goes to 4 seconds every time and counts back down to zero. When I hit it again it just does it over and over again. When I try to slot another power into tab from power window it tells me I cannot do it because the power is on cooldown, even though it's not. I CAN swap another power from my belt to tab and move steal time to that spot, and after that I can move things in and out of tab and they work properly, but then the key which has Steal Time on it (4,5,6 etc) will then be locked and tell me I cannot slot something in when the power is on cooldown, so it's a Steal Time thing not a tab-key thing. The only way to reset it is to log out and back in again otherwise that loadout is just locked for one power. I have been able to swap to another loadout and use all keys normally, but when I swap back to that loadout Steal Time is doing the exact same thing. I use this loadout all the time and it's mostly fine, just this happens in Castle Never, nowhere else and usually right after the first boss fight has finished with the beholder. It's really annoying me because it's my main AOE on that loadout.

c1k4ml3kc3

Yes, I agree. Steal Time is severely bugged. I was able to slot it twice on Wizard by some chance, too! Both on spell mastery and regular Encounter.

The cooldown animation for that spell is also broken within HUD as sometimes it shows that it is ready, although the timer still ticks.

So far the only repeating issue for me is the indication for the cooldwon not working properly.

fns2005

I've reported this also. It's buggy on Xbox as well.

darthpotater

Can confirm its happening too

nitocris83

Thanks for reporting folks!

aganway

Normally I would not ask and just wait and see when it gets fixed, but the appalling way this encounter is behaving I'm just asking if please they can make this a priority if it isn't already. As an Arcanist with my build this is really the only choice I have for an effective AOE encounter for hard mobs for team support, but Steal Time has been the bread and butter of many Wizards for as long as this encounter has been around anyway. Not only is it still locking up and rendering the loadout un-usable until I leave the instance at least once or twice a day but it is also failing to trigger at least half the time you use it, with only a few seconds of the animation happening then the counter going back up to countdown a few seconds again, tbh it's all over the place. When this encounter works as intended it is glorious which is why I am putting up with the fails and potential complete lock-ups (happened in my last dungeon run just before) because when it does work it works so well it's just worth taking the chance that it may be buggy, but the way it's behaving right now it's totally doing my head in and probably everyone else's too. Hopefully it's in the next patch or the one after that? *Gets down on my knees and pleads*

aganway

If it's any help to work out what's going on, I just had it locked again in CN and came out after we were finished and set it off to make sure it was working again and it did trigger fully, but when it did the timer went instantly to 9 for a moment then jumped up to 17 (where it is supposed to go to) then counted down normally. That is just not supposed to happen. Another thing it will also do sometimes I didn't mention is it will do the physical avatar action and affect the enemies as it should, but there is no audio or visual effect, as soon as avatar returns to normal it performs the action again this time with the visual and audio effect but no power attached to it. This reminds me of way back about a year ago I think it was I put a report on here that I was doing a second action after the encounter had completed, just the physical and nothing else, and this actually still occurs too. The encounter behaves as it should with all visuals, audio and effect on enemies plus avatar action, so is complete, but then the avatar does the action a second time immediately after with nothing else happening and just the movement and the grunts. Anyway, I thought I would mention this timer thing which just happened, because I clearly saw it jump first to 9 then to 17 which just should not happen and could be a clue as to what is going on with the timer. Timer on this power seems very confused to be honest (jumping all over the place) and seems to be the reason the encounter is playing-up so badly.

aganway

A guild mate told me today the Curse Bite on her Warlock also does the same thing, ie: locks up and won't work at all and will only work after leaving the instance. Today she had to close the game entirely to get it to come back again.

Steal Time timer is still behaving strangely, other day it jumped from 8 to 9 to 8 to 9 to 8 to 9 then 14 then counted down.

pelgrax

steal time has been bugged for the better part of 6 months or more . I have reported it a long time ago .

aganway

Steal time is still bugged, please fix.

aganway

Steal Time is still bugged, please fix.

aganway

Update on Steal Time. I have noticed it seems to be behaving better lately (ie trigger fails happening less often), however it is still not working properly. I just went and did an ME on my own to test it, the first 2 sections were mobs so I used my AOE/mob loadout which has Steal Time on tab (3rd section was boss on its own so I use a diff loadout with single target powers and no Steal Time), out of 31 uses it had 7 fails. By this I mean you hit tab to trigger it, the animation starts and he raises his arms, but they go back down again and power does not happen, counter then goes somewhere down around 4 or just over and counts back down again to zero. One time it did the strange extra animation move after it had finished which has been happening forever, but this does not concern me, it is when it does not trigger fully and the encounter does not work which is the issue. So as you can see, 7 times it did not work out of 31 times used is not a good result.