Whether it was intentional, or just [b]conveniently[/b] timed for when the Contest Mode for the Raid has ended, well now that's just a [i]mystery[/i] I suppose....
I guess so much for their 'disabled until fixed' mentality they had expressed when it was taken down. Because it's still broken - tested it today, still can swing endlessly without losing invisibility. So, really just looking like it was specifically to avoid it being used in the Raid to reduce amount of on-demand suppression available to guardians. As everyone assumed from the beginning anyway because of its timing.
-
5 RepliesThats not a bug though. Thats been a feature for over a year now. Throw invis smoke. Smack boss with sword while invisible for 12 seconds. They litterally added that feature on purpose.
-
2 RepliesI appreciate them turning it back on. It just makes the glaive so much fun to play with.... The question I have is "is it intentional that the melee is considered a kinetic attack, except for when generating orbs is considered".... Don't get me wrong with the orb to devour thing it would be hella broken if the glaive melee could generate orbs, but it complete a kinetic bounty I had which is weird.
-
2 RepliesAlso if you want to know. I suspect that what they intended was to have a brief period after your melee attack where it doesn't break invisibility. seeing as given the way you strike with the weapon it inevitably would accidentally melee after going invisible and break the invisibility.... I also think for processing reasons tehy probably didn't want invisibility triggering off and on at rapid intervals... So there is a small but present chance that it is working mostly as intended, just, the invisibility doesn't break for longer then intended. You can say what you want, if you wait a short period after you go invisible and then melee, it will break it.
-
7 RepliesWell, we did kinda assume that seeing as they addressed it in the TWAB… Also, would you rather have had them disable it for 2 days or nerf it for the rest of the season.