Guild Wars 2

(seewhatididthere? :P)

After playing for nearly a week, I’ve been noticing that my stealth sometimes almost instantly disappears. At first I thought it was a bug, but now that I carefully analyzed it, i found the cause: Barrage.

When you have barrage up, and you use stealth, as soon as one of the arrows hit your target, you will be revealed.

Is it a bug? Probably not. Stealth was always dispelled when the source dealt damage to anything. It’s something to take note of when using Barrage and Hunter’s Shot. I haven’t tested yet, but this would probably also be the case for traps.

I believe it’s any attack same thing for hunter’s call.

I frequently screw up my hunter’s shot stealth because of this. I’ll drop a barrage, then realize I need to get out of dodge, so I try to stealth…and immediately fail.

It’s something that’s going to take some getting used to, though I find in-combat stealth to be rather useless in PvE.

Quarktastic.1027:

I frequently screw up my hunter’s shot stealth because of this. I’ll drop a barrage, then realize I need to get out of dodge, so I try to stealth…and immediately fail.

It’s something that’s going to take some getting used to, though I find in-combat stealth to be rather useless in PvE.

It does take a bit of getting used to, especially since hunters shot turned from a “use this every time i comes back” skill to a “save this for the right situation” skill.

One thing I like to do is use hunters shot before barrage. That way you are stealthed during part of the the casting duration, and while barrage is going hunters shot is recharging so you can’t waste it.

I’ve actually found stealth to be really helpful, but its very situational. A good example would be the Arah run I did earlier today. When running past the risen I was able to use it on enemies to avoid getting hit, which actually saved my life. Against Lupi I used it when he used his AoE attacks in phase 2, which appeared to stopped the AoE from targeting me directly which made dodging it easier, and in phase 3 when he chased me and got close I used it to cause him to go after someone else in the distance, which saved me from getting hit.

Working as intended I’d say. I never even thought for a second that it would be considered a bug tbh.

Quarktastic.1027:

I frequently screw up my hunter’s shot stealth because of this. I’ll drop a barrage, then realize I need to get out of dodge, so I try to stealth…and immediately fail.

It’s something that’s going to take some getting used to, though I find in-combat stealth to be rather useless in PvE.

In most bosses in PvE you can stealth so they don’t put a red circle at your feet, i was doing this all the time on Subject Alpha to give myself some breathing room.

This is how stealth has always been on thieves. Any non-condition damage you deal will reveal you, no matter which skills were used first. Makes for all sorts of wonderful moments as a thief where you’re revealed by a clusterbomb you shot multiple seconds before stealthing.

Really, it should be changed, but I doubt it’d be easy for them to program.

Another thing to watch out for is projectiles that start channeling before you stealth will track you down as they normally would. Even if the channel has multiple projectiles like your longbow’s rapid fire, it’ll still follow you for every shot.

Yeah, I think it’s working fine. At the very least, the enemies will still have to re-target you if you get unstealthed immediately. Most people will misfire skills because of this unexpected “mini-stealth”

That’s how stealth works, it’s not a bug. Stealth is removed as soon as you deal direct damage to a foe, from any source. The exception is when you deal with conditions.

Ask mesmer using staff… It’s the main reason why i have given up on iElasticity. There is always a staff autoattack bouncing around instantly revealing you after cloaking.

You should be happy that it’s only a 12s CD (untraited) shot and not a 90s CD Massinvis