(edited by Ashantara.8731)
"Retreat!" = auto-attack
This bug still persists.
I can’t use the skill anywhere near enemies (or neutrals) as it initiates combat, thus severely slowing me down.
Please fix this bug: Since the release of LSW3 Episode 5, Retreat causes the Guardian to auto-attack the nearest red (i.e., enemy) or yellow (i.e., neutral) target, which is completely counter-productive as hitting a target results in the character’s movement speed to slow down (because “in combat”).
I am pretty certain that this is a recent thing and did not happen before aforementioned patch.
P.S. I had to deactivate auto-targetting because of this problem, which had never been an issue before.
This has been an issue since launch. I gave up reporting it after the third year or so.
it’s like this since day one , not really a bug : Guardian shouts are considered offensive skills.
Disable auto targeting in the options , make sure you don’t have a enemy selected before using a shout and it this ‘’ issue ’’ will not happen.
With auto targeting enabled in the options the AI will pick a target at the same time you use a shout. This why you need to disabled it.
(edited by Farming Flats.5370)
Please fix this bug: Since the release of LSW3 Episode 5, Retreat causes the Guardian to auto-attack the nearest red (i.e., enemy) or yellow (i.e., neutral) target, which is completely counter-productive as hitting a target results in the character’s movement speed to slow down (because “in combat”).
I am pretty certain that this is a recent thing and did not happen before aforementioned patch.
P.S. I had to deactivate auto-targetting because of this problem, which had never been an issue before.
This has been an issue since launch. I gave up reporting it after the third year or so.
Really?? Wow… That is a sad testimony of bug fixing then.
By the way, I think it wasn’t an issue a year ago — I am pretty certain I had auto-targeting active at the time. I only started noticing it a short while ago. Hmm. Maybe it was temporarily fixed?
it’s like this since day one , not really a bug : Guardian shouts are considered offensive skills.
Disable auto targeting in the options , make sure you don’t have a enemy selected before using a shout and it this ‘’ issue ’’ will not happen.
I did that to fix the issue already, but I don’t think it makes sense at all. Retreat, as the name suggests, is a “Let’s run for our lives, now!” skill, not a “Hey, you guys run, I keep fighting and possibly die all by myself!” skill.
(edited by Ashantara.8731)
The other option if you really need auto targeting is to set a hot key to stow your weapon. If you are quick enough you use a shout then quickly hit your stow weapon button to cancel the auto attack.
The other option if you really need auto targeting is to set a hot key to stow your weapon. If you are quick enough you use a shout then quickly hit your stow weapon button to cancel the auto attack.
or you could look up at the sky. it stops you from targeting anything, mostly. I do it often with rush on warrior GS
| 61 Asura | 5 Charr | 2 Norn | 1 Human | 1 Sylvari |
The other option if you really need auto targeting is to set a hot key to stow your weapon. If you are quick enough you use a shout then quickly hit your stow weapon button to cancel the auto attack.
Yes, know that too, but still, it is yet another workaround, not a solution. I wish for Anet to finally fix this!
Please fix this bug: Since the release of LSW3 Episode 5, Retreat causes the Guardian to auto-attack the nearest red (i.e., enemy) or yellow (i.e., neutral) target, which is completely counter-productive as hitting a target results in the character’s movement speed to slow down (because “in combat”).
I am pretty certain that this is a recent thing and did not happen before aforementioned patch.
P.S. I had to deactivate auto-targetting because of this problem, which had never been an issue before.
This has been an issue since launch. I gave up reporting it after the third year or so.
Really?? Wow… That is a sad testimony of bug fixing then.
I’d suggest that, perhaps, you are mistaking “working as intended” for “failure to fix a bug”. If anet don’t see this as wrong, because it is the intended function (ever if we don’t like it), not “fixing” it makes sense, no?
Just because it’s a shout doesn’t mean it must have the exact same mechanic as other shouts. It’s clearly a flee-the-scene skill and thus should be treated as such. It makes no sense to result in you being slowed down and thus trapped at the scene (and likely killed).