Guild Wars 2

I’ve been keeping an eye on the “Known Issues” page, and despite this bug having been reported multiple times since the July 26 update, it hasn’t made it to that list. I assume the in-game bug reports and forum posts have fallen through the cracks.

So, to reiterate:

Banner skill #5, “Plant Standard,” doesn’t work. I mean, it doesn’t actually do anything. Pressing the button has no effect at all. Doesn’t even put it on cooldown. It’s like it may as well not exist.

Thank you.

This is true even if another person, regardless of profession, grabs the banner. Skill #5 does not work for anyone.

DKShang.8792:

This is true even if another person, regardless of profession, grabs the banner. Skill #5 does not work for anyone.

Right.

Also, it’s for all the banners. I’ve tried them all, even Battle Standard, thinking that its slightly different skill bar might make a difference. But it doesn’t. Skill #5 doesn’t work for it, either.

I would really like it if we could at least get some confirmation if this issue, as well as some of the other currently aggravating warrior bugs (Head Butt self stun breaking trait and rune triggers and F1 burst skills randomly firing by themselves), are being looked at. It’s so hard to know if they’ve caught the attention necessary for fixes, since they’re not being added to the known issues tracker, when it’s been almost a month since the patch released.

F1 Burst casting by itself

Head Butt self stun breaks trait and rune triggers

Muhandias.7453:

I would really like it if we could at least get some confirmation if this issue, as well as some of the other currently aggravating warrior bugs (Head Butt self stun breaking trait and rune triggers and F1 burst skills randomly firing by themselves), are being looked at. It’s so hard to know if they’ve caught the attention necessary for fixes, since they’re not being added to the known issues tracker, when it’s been almost a month since the patch released.

F1 Burst casting by itself

Head Butt self stun breaks trait and rune triggers

The known-issue tracker is misnamed. It’s a manual list curated by a single dev, who tries to figure out which issues are the most important to the greatest number of players. Translation: if your issue is on it, great — you can keep track of progress. If it’s not, it doesn’t mean anything (good or bad); it just means it’s not on the list.

Obviously, it would be better if the tracker was automated and the devs routinely updated issues with language that would be fair to post publicly.

In the meantime, you can presume that anything you report via the in-game /bug tool gets added to their internal list. The more details you give them, the easier it is for them to troubleshoot and ultimately fix.

We can’t (again, unfortunately) speculate as to the progress or the priority.

I don’t mean to suggest that we stop asking for status reports — on the contrary, I think it’s good that ANet gets reminded that we still want stuff fixed. I do mean that there’s little value worrying about it after that; we aren’t likely to influence the priority except accidentally.

I did an in-game bug report on this a few days ago.

cormega.6238:

I did an in-game bug report on this a few days ago.

Yeah, I did that a few weeks ago.

hm Yea I seen this bug pick up a banner and literally can’t get rid of it till it wears off

Rei Hino.5961:

hm Yea I seen this bug pick up a banner and literally can’t get rid of it till it wears off

You can still get rid of the banner by pressing your “Swap Weapons” keybind.