Guild Wars 2

Recently I’ve been playing P/D thief, and playing around with the builds a bit, I thought I found something I liked. One of the traits in Shadow Arts, “Hidden Thief” grants two seconds of stealth on steal.

In normal play (on D/D thief, for instance), one would be able to execute a steal, thus teleporting to their target and cloaking for two (technically, three due to a prior minor trait) seconds. This happens even when you take the trait “Mug,” and whether you are in or out of combat.

While using P/D however, while in combat, I do not stop autoattacking after executing a steal, or am simply unable to use my special 1st slot skill, and just continue to autoattack. It seems to function just fine outside of combat. I can steal>teleport>cloak>sneak attack. The only way I have found to fix this is to turn autoattack off.

If you want to try to duplicate this problem yourself, my traits are:

15/0/20/0/30 (I am level 75)
Major traits:
III
VI, VIII
V, VII, XII

I thought this might be an issue caused by “Sleight of Hand” (daze on steal), but I’ve tried it without, and the problem still seems to persist. Could there possibly be a mechanic I am overlooking? Otherwise-pretty nice build.

I tried replicating this. The problem is actually with the flight time of the bullet. A bullet you fired before stealing strikes the target after you entered stealth, causing the Revealed effect and preventing you from using your stealth attack. Not a bug as far as I can see, you’ll just need to sheath weapon before stealing to make sure you stay stealthed.

Prahl.1057:

I tried replicating this. The problem is actually with the flight time of the bullet. A bullet you fired before stealing strikes the target after you entered stealth, causing the Revealed effect and preventing you from using your stealth attack. Not a bug as far as I can see, you’ll just need to sheath weapon before stealing to make sure you stay stealthed.

I hadn’t thought of that! I played around a bit more, and this seems to describe the problem pretty well. I don’t appear to have the issue at shorter ranges, so I’ll find a workaround.