learning how to throw yourself at the ground and miss.
Target Nearest Enemy
learning how to throw yourself at the ground and miss.
It also doesn’t target anything not in front of you… I really hope it’s a bug…
Oh did it stop targeting things behind you?
It also doesn’t target anything not in front of you… I really hope it’s a bug…
Oh did it stop targeting things behind you?
This would make me happy.
In my case the system does actually favour targeting things behind me / to the side of me rather than targeting the sole enemy in front of me :/
In my case the system does actually favour targeting things behind me / to the side of me rather than targeting the sole enemy in front of me :/
yeah that’s the way it’s been for quite a while now. Also fun to select the champion at the end of a hallway like in coe
Targeting has been broken for a loooong time now… https://forum-en.gw2archive.eu/forum/support/bugs/Targeting-Still-Broken-Please-Fix-It/
Probably one of my most clicked buttons when playing conquest, please fix :’(
Target Nearest Enemy no longer works out of line of sight. Not sure if this is intended =/
Not only is Target Nearest just picking up enemies that are in your Line of Sight, but the enemy also has to be in your Field of View now. So, if the enemy is behind you (not on your screen, per se) but on level ground, Target Nearest doesn’t pick him up now. (WOW…totally kitten useless!) Bug or not… this is a HUGE step backwards imo. x(
I don’t “Fear the Reaper”…“I FEAR PATCH TUESDAY!!!” :/
Anet, since constant inadvertent rollbacks are happening anyway, please just roll back to Monday’s (May 18th’s) version until you have time to properly test this May 19th patch and fix it w/o subjecting your player base to this plethora of bugs. (Things were just getting stable again from the March 16th patch debacle, and I was again enjoy GW2. But now we’re going through the same magnitude of breakage here with this May 19th patch. )
(edited by Krypto.2069)
I’m just gonna bump this so devs hopefully see it
learning how to throw yourself at the ground and miss.
I’m going to give it a bump also because borking targeting and entire classes should be addressed along with pushing a patch before other bugs should have been addressed like not being able to use the hall of monuments to get your rewards…..
To make it a bit less frustrating,try using the targeting option Next enemy instead of Closest enemy.The Next enemy option will usually select players over anything else while the Closest enemy option just picks Anything it can find from pets to npcs to walls to whatever..
Not only is Target Nearest just picking up enemies that are in your Line of Sight, but the enemy also has to be in your Field of View now. So, if the enemy is behind you (not on your screen, per se) but on level ground, Target Nearest doesn’t pick him up now. (WOW…totally kitten useless!) Bug or not… this is a HUGE step backwards imo. x(
Actually, it was the previous (or even initial) behavior: targeting was used to pick up only enemies in your field of view and not behind you. It was changed a while back and a few players complained (even myself, I don’t see a point of having a “superpower” that allows you to know about an enemy sneaking up behind you :P), and the main issue with it was that targeting would prioritize enemies out of your view or out of reach over those right on your throat.
More about it here: https://forum-en.gw2archive.eu/forum/support/bugs/Targeting-Still-Broken-Please-Fix-It/
Not only is Target Nearest just picking up enemies that are in your Line of Sight, but the enemy also has to be in your Field of View now. So, if the enemy is behind you (not on your screen, per se) but on level ground, Target Nearest doesn’t pick him up now. (WOW…totally kitten useless!) Bug or not… this is a HUGE step backwards imo. x(
Actually, it was the previous (or even initial) behavior: targeting was used to pick up only enemies in your field of view and not behind you. It was changed a while back and a few players complained (even myself, I don’t see a point of having a “superpower” that allows you to know about an enemy sneaking up behind you :P), and the main issue with it was that targeting would prioritize enemies out of your view or out of reach over those right on your throat.
More about it here: https://forum-en.gw2archive.eu/forum/support/bugs/Targeting-Still-Broken-Please-Fix-It/
Shadow, thanks for the info! And, yeah, I know it’s flipped-flopped a few times.
You know, I think it was nice to be able to have a sonar type of targeting skill. And, yes, yes… perhaps it was a bit over the top. I get that. But I would like for Anet to put such changes, if intended, into the kitten release notes! This way there is no speculation as to whether a skill has changed by design or if it’s a bug… or if it’s a combination of both (bug and design) that has a skill in its current state, i.e. – the whole stealth/reveal thing seems to be a little of both.
In short, if a skill has changed by design, put it into the notes. If it’s a bug, it would be beneficial to all if Anet would come to the thread that’s talking about the bug and at least comment on it, like with the stealth/reveal issue.
Anet,
This is not a “my outfit is not hanging on my large Norn behind correctly” issue… This is TARGETING! It would be nice to have some official words on this change. (I don’t want to start adapting to the current way Target Nearest is working only to have it undone in a week because it was a bug.)
Some communication on this, Anet, please?
Shadow, thanks for the info!
And, yeah, I know it’s flipped-flopped a few times.
You know, I think it was nice to be able to have a sonar type of targeting skill. And, yes, yes… perhaps it was a bit over the top.
I get that. But I would like for Anet to put such changes, if intended, into the kitten release notes! This way there is no speculation as to whether a skill has changed by design or if it’s a bug… or if it’s a combination of both (bug and design) that has a skill in its current state, i.e. – the whole stealth/reveal thing seems to be a little of both.
In short, if a skill has changed by design, put it into the notes. If it’s a bug, it would be beneficial to all if Anet would come to the thread that’s talking about the bug and at least comment on it, like with the stealth/reveal issue.
You are welcome. And yeah, I can’t agree more. Changes like that should be on patch notes indeed but the same thing happened when that behavior was changed (when it started targeting enemies out of view): nothing on patch notes as far as I recall. Even in this case, I’m not so sure what was the real and original intended behavior: if targeting being able or not to target enemies out of view; but what I’m sure is that it has hardly worked properly in both behaviors, that thread is there to confirm it.
I most certainly hope this isn’t an intended change… I, as many others, have gotten used to using this a lot and changing it without even announcing anything about it is a real game changer for people like me, I’m sure. Now let’s just hope they revert it back asap.
I most certainly hope this isn’t an intended change… I, as many others, have gotten used to using this a lot and changing it without even announcing anything about it is a real game changer for people like me, I’m sure. Now let’s just hope they revert it back asap.
Well, what if the previous behavior (one that it would target enemies behind you) were the real bug and not this one now? As long no official responses are given one can only suppose or guess which one was the intended.
So is this a bug or a feature? I had gotten used to using it a lot, and having it just taken away from me is quite annoying. I need to at least know if it’s going to get reversed or what is going on :/
Just to bump this and hope for a DEVs answer IF targeting IS ever going to actually work ..
Tab target DOESN’T EVER choose the target right in front of you .. IT will target one at a range (so you pull a huge extra number of mobs potentially) or anywhere BUT the one that is probably hitting you at that time
I really hope they one day fix this
Just to bump this and hope for a DEVs answer IF targeting IS ever going to actually work ..
Tab target DOESN’T EVER choose the target right in front of you .. IT will target one at a range (so you pull a huge extra number of mobs potentially) or anywhere BUT the one that is probably hitting you at that time
I really hope they one day fix this
Just check the link I posted above, targeting has several issues for some time now and I hope so too.
I noticed this today after thinking noone was nearby (my target nearest bind didn’t target anything) and being badly surprised by someone very being very, very close :P
It now will target the nearest enemy on the screen. This is not line of sight dependent, it is strictly field of view, as other posters have mentioned.
I’m not going to complain because it probably should have worked this way all along, but I would really have appreciated a heads-up in a patch note.
unofficial theme song of the Nightmare Court
In my case the system does actually favour targeting things behind me / to the side of me rather than targeting the sole enemy in front of me :/
yeah that’s the way it’s been for quite a while now. Also fun to select the champion at the end of a hallway like in coe
You two are talking about Target Next. It’s been weird for some time. This thread is about Target Nearest which significantly changed in the last week (without a patch note).
unofficial theme song of the Nightmare Court
Bump
Broken for me as well, but I think it only started within the last week or so. It will only target things nearly directly in front of me and within LoS.
This needs to be answered
anything yet?
“Revenant is actual proof that devs read the necromancer forum” – Pelopidas.2140
Anet, I have seen you really screw up some serious kitten because you are too busy making dresses so everyone can be pretty instead of fixing your bugs, but this new in your face targeting BS is seriously f’d up. And sometimes, it still doesn’t take with your opponent gnawing on your face already. And now you are ignoring everyone’s question about it. Typical.