Guild Wars 2

I noticed last night that Pulling someone, or Knocking them back will put you in combat now, even though you did no damage to them.

Which adds more frustration to Mesmers. Our only reliable source of swiftness is Temporal Curtain, which seeing that crippling something puts you in combat from an update awhile ago, I would use Into the Void soon after I got my swiftness so nothing would run across and put me in combat. Now, as I found out last night, if I use Into the Void and pull something, I’m stuck in combat anyway. It doesn’t cripple the “enemy” or anything, just screws you over on trying to get anywhere a little quicker.

I noticed while swimming, I aggroed a Skale, but he hadn’t hit me, so I was still out of combat. I use Slipstream to get away from it quicker. Well it hit the line, got knocked back and put me in combat.

Not sure about other professions, but this is what I saw last night.

In my opinion we should automatically get in combat if we get close enough to any enemy.

Good. Pushing, pulling, shoving, and/or giving wedgies is an act of combat and should be treated as such.

If you do any offensive move towards an enemy, you should be put in combat. Period.

Sevans.4619:

Good. Pushing, pulling, shoving, and/or giving wedgies is an act of combat and should be treated as such.

The thing is though, this has quite negatively impacted guardians and mesmers… who already lacked in mobility and this only makes that worse. So while that warrior goes charging by the guard/mesmer are trying to get their swiftness applied and in the process actually slowing themselves down sometimes…

Wethospu.6437:

In my opinion we should automatically get in combat if we get close enough to any enemy.

Totally agree, though I think I know some people who would smack me for saying it.

Wethospu.6437:

In my opinion we should automatically get in combat if we get close enough to any enemy.

I agree with your opinion on the matter.
I’ve also made mention of supporting something like this here in regards to skipping enemies and enemy aggro behavior.

I’ll agree it makes sense, just frustrated as a Mesmer player because we have no real way of having swiftness now without putting ourselves in combat. Or sacrificing offense/defense because of having to use Traveler Runes.

That and Anet said nothing of it in patch notes.

ammayhem.5962:

I’ll agree it makes sense, just frustrated as a Mesmer player because we have no real way of having swiftness now without putting ourselves in combat. Or sacrificing offense/defense because of having to use Traveler Runes.

Equip centaur runes and use mantra of recovery for perma swiftness. Not really sacrificing any combat potential since you weren’t planning on getting into combat anyway.

Jerus.4350:

The thing is though, this has quite negatively impacted guardians and mesmers… who already lacked in mobility and this only makes that worse. So while that warrior goes charging by the guard/mesmer are trying to get their swiftness applied and in the process actually slowing themselves down sometimes…

I may be mistaken, but aren’t those classes supposed to struggle with mobility, anyway?

draconx.3102:

ammayhem.5962:

I’ll agree it makes sense, just frustrated as a Mesmer player because we have no real way of having swiftness now without putting ourselves in combat. Or sacrificing offense/defense because of having to use Traveler Runes.

Equip centaur runes and use mantra of recovery for perma swiftness. Not really sacrificing any combat potential since you weren’t planning on getting into combat anyway.

Apparently you’ve never been in WvW and trying to run to the defense of a Keep and your path leads you through moas or minotaurs. Combat is fully expected, but against the invading server, not some stupid moa.

Made a post about this in the bug section and it appears to be global to all non-damaging knockbacks as far as I can tell. I really don’t care much since it barely affects the way I play, but a change in mechanics like this really should have been listed in the patch notes (assuming it’s intended).

Sevans.4619:

Jerus.4350:

The thing is though, this has quite negatively impacted guardians and mesmers… who already lacked in mobility and this only makes that worse. So while that warrior goes charging by the guard/mesmer are trying to get their swiftness applied and in the process actually slowing themselves down sometimes…

I may be mistaken, but aren’t those classes supposed to struggle with mobility, anyway?

Yup, they are, but did they really need to be pushed even further back?

The change makes sense, but the relative mobility between classes IMO didn’t need to be spread even further apart.

Let’s not forget, this may also affect how Mesmer’s would be able to run in hide in a Keep that is overrun so they can later port their team back in. Maybe it won’t be a factor, maybe it will.

I always found it odd with my guardian when I hit RETREAT, he actually tries to attack rather than retreat.