Guild Wars 2

As I have been playing in level 80 PvE, PvP, and WvW over the past few weeks I have seen more and more instances of iWarden not attacking at all. I barely experienced this in my 1-79 career but have really seen it take off these past few weeks (I can’t say for sure if it is tied to the recent patch or not. I wasn’t monitoring it that closely then).

So, I thought it may be useful if we gathered a list of confirmed circumstances that will make the iWarden fail in some way. I searched around and couldn’t find a similar list. Hopefully this can serve as a guide for when using iWarden is risky and maybe help Anet’s developers (assuming they read this).

Here are several circumstances that I can reliably say I have seen iWarden fail at least 50% of the time:

1. The iWarden and the target are at different heights. I notice this when summoning an iWarden on a staircase – it almost never begins attacking.
2. When I summon iWarden while on the move.
3. If the opponent is currently in the middle of a dodge roll animation. Unknown if evade skills (like Blurred Frenzy) also cause this.
4. If the opponent is currently knocked prone due to an effect like Temporal Curtain’s shatter effect.

These are the only ones I have been able to notice over and over again recently. Have you all seen these as well? I would love some feedback and maybe additional circumstances where using iWarden is risky.

Thanks!

I’ve had my Warden fail when cast almost point blank on a NPC Scout that was standing stock still and firing at me…..

I applaud your initiative but I don’t think you’ll find any specific avoidable action or situation which causes failure if simply casting it on a stationary NPC is enough to break it. Also not doing this will save you the anger and despair which will inevitably come when you and the community produces an exhaustive list of failure situations plus potential coding causes/solutions which Anet then ignores.

Lord Jim.3971:

I’ve had my Warden fail when cast almost point blank on a NPC Scout that was standing stock still and firing at me…..

I applaud your initiative but I don’t think you’ll find any specific avoidable action or situation which causes failure if simply casting it on a stationary NPC is enough to break it. Also not doing this will save you the anger and despair which will inevitably come when you and the community produces an exhaustive list of failure situations plus potential coding causes/solutions which Anet then ignores.

They seem to give some attention to the mesmer bugs thread on the Game Bugs forum. I was hoping to collect a few instances here then post them there in one reply for easy reading.

But you’re probably right, it’s probably a waste of time. I’m not convinced good project management is at the top of Anet’s skillset.

iWarden fighting the 4 golems at the end of the harpy fractal… Target a golem it will fail FAR more often then it will actually start attacking (actually I don’t think I’ve ever seen it begin attacking).

iWarden will never attack the 4 golems at the end of the harpy fractal. Unfortunately, I still use focus for the relfect from curtain otherwise I would use pistol.

Also iWarden does not attack grubs spawned by Lupi.

As Veruah Posted, I agree these are the times when iWarden normally will bug.
However I wouldn’t get your hopes up, I doubt Anet will fix them. Also if you end up putting this in the bug forum create a new thread. The instructions they have for the bug forum explain they wont look at long threads like the mesmer bug compilation thread we have going on there.

A lot of these can be explained by the “most times there is a slope” rule. In particular, Harpy Fractal and Arah have a lot of fun locations where the ground slopes. Those seem to confuse the wardens very often.

maxinion.8396:

A lot of these can be explained by the “most times there is a slope” rule. In particular, Harpy Fractal and Arah have a lot of fun locations where the ground slopes. Those seem to confuse the wardens very often.

In the harpy fractal at the end on the golems there isn’t a slope. I believe its because they start out as friendly before attacking the asura boss. That is when they become aggressive but the wardens do not pick up on that.

My wardens otherwise have few problems in that fractal, they work alright on the small sloped platforms that the harpies are on. If they don’t attack at first they will at least start to at some point.

I’m not as certain on the grubs with lupi but yes it could be terrain.

Edit: they also glitch on immobile targets, especially targets that are not aggressive like the totems in HOTW that gives buffs to the boss. This could also be why they don’t attack the golems as they start out as immobile targets before attacking the asura in the harpy fractal. I also forgot to mention they never attack mossman if he is near the water in swamp fractal. I think this is because they have tried numerous times to fix the glitch people do with him and it results in failed iWardens, but they will not attack, and they will not move when summoned in that area.

Andraus.3874:

maxinion.8396:

A lot of these can be explained by the “most times there is a slope” rule. In particular, Harpy Fractal and Arah have a lot of fun locations where the ground slopes. Those seem to confuse the wardens very often.

In the harpy fractal at the end on the golems there isn’t a slope. I believe its because they start out as friendly before attacking the asura boss. That is when they become aggressive but the wardens do not pick up on that.

My wardens otherwise have few problems in that fractal, they work alright on the small sloped platforms that the harpies are on. If they don’t attack at first they will at least start to at some point.

I’m not as certain on the grubs with lupi but yes it could be terrain.

I’m 99% certain that the entire arena is slightly sloped at the final boss of the harpy fractal (it’s hard to tell because of the perspective).

Again, this isn’t a 100% thing— sometimes it works fine on slopes (for example, there are some spots in Arah where it’s fine— most spots where you pull Risen Hunters for example). It’s just that whenever I do see a fail, there’s a slope. A slope doesn’t guarantee a fail, though.

See these two videos: https://www.youtube.com/watch?v=rqgJR5NUdTo where wardens fail, and https://www.youtube.com/watch?v=8fCfpKZ0_s8 where wardens succeed. The only difference between the two? We pushed alphard off the top of her little hill, onto the tiny slope, in the first one. Watching it more closely, it looks like she bugged when she walked around to the other side— so this was even after she was on the slope, and back in the center. Very weird.

Your mileage may vary, of course.

@maxinion:

Slopes may be a contributing factor, but they aren’t the whole story. The queen’s gauntlet arena was perfectly flat. I killed deadeye dunwell hundreds of times, 0 bugs. You fight subject 7 or the crew of the pirate ship Ravenous, nonstop warden failures.

The final fight in the grawl fractal is uneven ground, but generally flat. Nonstop bugs.

The asura path in CM has a room filled with snipers up on a nice and flat boardwalk. Wardens bug out at an over 90% rate on those mobs, but 0% on the boss below.

Fay.2357:

@maxinion:

Slopes may be a contributing factor, but they aren’t the whole story. The queen’s gauntlet arena was perfectly flat. I killed deadeye dunwell hundreds of times, 0 bugs. You fight subject 7 or the crew of the pirate ship Ravenous, nonstop warden failures.

The final fight in the grawl fractal is uneven ground, but generally flat. Nonstop bugs.

The asura path in CM has a room filled with snipers up on a nice and flat boardwalk. Wardens bug out at an over 90% rate on those mobs, but 0% on the boss below.

That’s true about Subject7 and Grawl, but I’ve never had a problem in CM (at that spot at least). Good points though— it’s incredibly inconsistent :\