Guild Wars 2

I don’t know if this has already been mentioned (I did use the search function and found nothing on ‘axes’ or ‘necromancers’!) but using the axe autoattack on ambient creatures such as rabbits puts us in combat when I’m pretty sure that it shouldn’t.

Using the autoattacks on any other of the necromancer weapons doesn’t put us in combat as far as I’m aware so this is something that needs to be fixed on the axe.

Thanks.

Its due to the fact that the axe auto attack applies vulnerability. In the last patch they made it so that applying a condtion that does no damage will now put you into combat.

Not saying it isn’t a bug. I think it is definitly an unintended side effect on ambients

Oh okay, I was wondering. I only noticed because I use axe a lot and this was pretty annoying.

yup, happens on warrior sword 1 now (bleed) axe 3 (cripple) but interestingly it doesnt do it on hammer 3 which is a cripple.

I’m not sure I understand why you think this is a bug. You’re “attacking” something. That’s supposed to put you in combat. Why wouldnt it?

I think it may be a possible issue because of the inconsistency. Why should one type of attack put you in combat and another not? I don’t mind either way but it probably should be universal to avoid confusion and constant bug reports.

Malganis.7468:

I’m not sure I understand why you think this is a bug. You’re “attacking” something. That’s supposed to put you in combat. Why wouldnt it?

Previously attacking an ambient creature didnt actually put you into combat. But they changed Conditions, that a condition applied without direct-damage component still puts the player in combat.

However, as a result abilities that deal direct-damage AND a condition now put the player in combat against ambient creatures. But using abilities without a condition do not, just like before.

Something like that.