Guild Wars 2

…I will survive; though I do think that it’s a teat beet ridiculous when I hop on the forums only to find an insane amount of QQing that things will never be fixed, that A-Net doesn’t care, and that they aren’t paying anyone any attention etc, etc, etc

Really? Could you imagine running a 24/7 virtual daycare for all of us??

By Balthazar’s beard, that spat’d be muckin awful…

Now, for my QQ “why me n’ my class” rant; considering how popular they seem to be these days:

Completely disabled A-Net? Really?…An entire GrandMaster trait just disabled (not merely modified, replaced, or out right nerfed) while we wait, indefinitely, for it to be fixed? Any other class(es) lose an(y) integral trait(s) indefinitely yet? Engis, Wars, Mes, Nec?…Any of the “other” particularly “OP” classes during this FotM?

Nope, not that I know of; if there are any, please feel free to inform and save me from my own misinformation…

I didn’t use that trait because it was broken, by any means. It just so happened to pair particularly well with my SymMed-Guard build, at the time. I don’t PvE anymore as I’ve gotten most of the gear I’ll ever want/need and am satisfied (sPvP n’ Gemstore for me); so that whole Teq thing n’ WvW is, on my end, like getting punished here in the US for something someone did in Taiwan and/or Western Samoa…

…But hey, muck it, avoided Burn Guard like the plague post-patch due, in part, to everyone QQing about it and the amount of cheese it apparently holds within its folds (phenomenally moist mental imagery there ay folks??)

Oh well, considering my well-rounded SymMed build has just lost a key component; BURN GUARD FTW, BURN GUARD FOREVER, BURN GUARD 4 LIFE!!!

Annnnnd now that all that’s out there, cool beans, I feel better; maybe all this QQing is just a cathartic way for people to release their fanatic frustrations over particular pent up passions…

PS: Though, when I say “passions”, I don’t mean folks who complain about aspects of the game so incredibly trivial that no one else even bothers to notice and/or mention them; to those people, there’s the door, we will not miss you…

Sincerely,
Gilded Guardian – ;333

Palomid.9256:

Completely disabled A-Net? Really?…An entire GrandMaster trait just disabled (not merely modified, replaced, or out right nerfed) while we wait, indefinitely, for it to be fixed?

Did it cross your mind at all that they didnt have the option of leaving it ingame until fixed? With how powerful of a bug it was, I applaud Anet for disabling it before it came close to being an economical impactor. Modifying it, which by definition is HOW they’d fix it, without removing it first, could lead to even more disastrous occurrences. Replacing it would mean finding another trait to slot in the meantime, which could become just as broken, or worse. As innocuous as the trait looked, there’s something somewhere in the code throwing a wrench of epic proportions. That somewhere is just as likely in the trait’s code itself as it is in the combat code.

Sorry, I dont play guard, what is the bug?

@BasSky:
Yes, it did cross my mind that yadayadayadaetcetcetc…

However, Guard is not the only class with ball busting bugs atm. Yet they’re the only class, in the history of GW2 [once again, correct me if I’m wrong] (played GW1 too; traits didn’t exist then the way they do now), who’s had a trait completely and utterly disabled, indefinitely, due to faulty fine tuning on the developers end; oh, and hot fixes have kinda sorta been how they’ve fixed just about every single issue to date when it comes to this particularly precious title…

…Also, this whole thing isn’t new news; I was reading postings about this soon after the June 23rd patch (yes that is recent but by no means is it breaking news, pun completely and utterly intended), so just now disabling it as if it happened a few hours ago and they’re catching it real quick like is a bountiful buncha bologna

I’d also like to restate that, for the most part, I commend A-Net for doing such an incredibly commendable job; merely meant to add a quick vent to the chimney of chipper chimers who’ve all got such nice things to say about things they don’t even semi-comprehend. My only “complaint” is that I don’t think this was the right way to go about fixing this particular issue; but hey, then again, what do I know right?…

@RogPot:
No worries bud, all is well, there was an issue with the late Symbolic Avenger trait that caused ridiculously large amounts of dmg to be dealt in tremendously small amounts of time with incredibly copious numbers of Guardians all banding together to break the game (weakened as it may’ve been by the massive shift) for themselves and others…
More info in the link below mi amigo:
https://forum-en.gw2archive.eu/forum/professions/guardian/Update-Symbolic-Avenger-Trait/first

Sincerely,
Gilded Guardian – ;333

Is it not sad that people need to pound the message home by copious numbers of people before they do anything?

Palomid.9256:

@BasSky:
who’s had a trait completely and utterly disabled, indefinitely

You make it sound as if it will takes months or years when you say it like that. I’m sure it won’t be long at all.

Just take it easy. It was something that was ruining the experience for most of the playerbase. Guardians can simply switch traits in the meantime, even if it is inconvenient. The needs of the many yadayadayadaetcetcetc…

Hyble.4271:

Palomid.9256:

@BasSky:
who’s had a trait completely and utterly disabled, indefinitely

You make it sound as if it will takes months or years when you say it like that. I’m sure it won’t be long at all.

Just take it easy. It was something that was ruining the experience for most of the playerbase. Guardians can simply switch traits in the meantime, even if it is inconvenient. The needs of the many yadayadayadaetcetcetc…

No we can’t, there are not other grandmaster traits that are useful in that line.

@Storm:
Yush, yush it is…

@Hyble:
When someone’s on their way over to your place and informs you that they’ll get there when they get there; would you be expecting them to arrive early, on time, or late?…

And believe you me, I’ve got no problem rollin with the punches, been doin it darn near all my life n’ don’t plan on quittin anytime soon; however, all the fresh victims over at the Intensive Care Unit’s – QQ – Burn Division aren’t so satisfied with this exceptionally suitable swing n’ switch…

Sincerely,
Gilded Guardian – ;333

Bugs happen, welcome to gaming. It was better to disable it and work on a solution than any of the other options you suggested, which would take more time, coding changes, and possible break further things.

@Hyble:
Right, fer sure, hot fixing issues like they’ve done this entire time is sooo inefficient; what’re those whack grass motherflowers thinkin when they pull that spit??

Sincerely,
Goaded Guardian – ;333

So you’re saying you think they have the fix done and are just refusing to implement it???

@Hyblebud:

No, but I do believe they’ve had more than enough time (short a span as it may seem; life moves rather quickly these days) to work on some sort of short-order/hot/quick fix; OR, at the very least, something band-aid-esque compared to complete and utter Civil War style limb removal, indefinite as it may be…

Blahblah,
Gilded Guardian – Blah

Just want to let you know, that Guardians are not the only class to have one of their traits disabled. Engis had one of their traits disabled as well. Just wanted to let you know on that

Rogue Potato.4723:

Sorry, I dont play guard, what is the bug?

Guardians had a trait that increased their damage by 10% when the target was in a symbol and it was bugged so it counted that +10% boost from every symbol affecting the target. People abused it in masse by piling on guardians with hammers that produce symbols at the end of each autoattack chain.

End result was that a single guardian could do more dmg than 10 people of any other class in places like tequatl and wvw.

Taku.6352:

End result was that a single guardian could do more dmg than 10 people of any other class in places like tequatl and wvw.

35k hammer AA crits /snerk

@OP, chill out and relax, go play another game or something. Hyperboles and exaggerations have no place here. You seem like you’ve got little to no understanding of coding, which means you dont understand that while something may look simple on the surface, it’s a massive cluster-kitten right under it. Especially when it’s something that they’re going to need to basically follow every single reference, call, and variable, among other things, to see if SOMETHING, somewhere, is either doing something it shouldnt, or not doing what it should, or both. Given that it’s a trait, it could be something as simple as a missing qualifier (basically a “symbol.ownership == self” sorta thing), to something as complex and nightmarish as going through the rat’s nest of the Combat System code.

Granted, my involvement with coding is merely academic and hobby related (kitten able required java course….), but it DOES give me insight on just what a mess is involved in finding a bug. Believe me, nothing’s worse than a bug caused by the code not being wrong, but by the code being right in the wrong way.*

*I’ve spent nearly two weeks before trying to find the cause of a similar bug in a project. I was only able to fix it by butchering it into a less efficient form. “Coding, where being too efficient can actually be a problem.”

It’s a GM trait. It needs to be “special” enough but not game breaking like it is now. It’s not like “oops we forgot to toggle reveal when the power is used” which is likely a table entry and therefore can be quickly hot fixed in a day or two.

FYI, Engineer has had a trait disabled too Just so you know.

@Berelious:
Indeed indeed mi amigo, had read Señor TimberWolph’s response earlier on but by the time I’d seen his rejoinder this thread had gotten a page or two back and I didn’t really feel like bumping it back up to page 1 merely to inform him that I’d seen said post lol…

…Buuut then it got bumped up anyway so here we are and I, in all honesty, thank you for the information bud; truly do appreciate it

Sincerely,
Gilded Guardian – ;333

OP, you should take a gander at this and this.

It’s unfortunate you’re unhappy about the temporary fix, but it doesn’t cripple your ability to enjoy the game like it would have crippled anyone’s ability to seriously play in WvW; siege would have been pointless, upgrading keeps would have been pointless, escorting supplies would have been pointless, capturing ruins would have been pointless. For an entire week it would have been nothing but guardian and engineer zergs spamming symbols and grenade barrages, destroying absolutely everything and everyone in their path with virtually no effort.

Yes, it’s a shame ANet didn’t jump on fixing it earlier like they did the unintended boon sharing, but that’s no reason not to disable it after everyone realized how severe the bug really is. This is very much a case of “better late than never”.

Ayyy that’s just how Anet rolls. I didn’t think it would take nearly 3 years for them to pull the Smiter’s Boon card again though.

http://wiki.guildwars.com/wiki/Smiter%27s_Boon_%28PvP%29

The OP harms their own argument with over-the-top hyperbole. Everyone agrees that it’s bad for the game to have a broken GM trait. Everyone agrees that it’s an extreme reaction to disable the trait. Everyone agrees that it ought to be fixed ASAP.

Since “everyone” includes the programmers at ANet, I have trouble understanding why people think that the devs there are purposefully delaying a “good” solution to the problem, rather than the dirty bandage they gave it last week. If it was easy, of course they would have fixed it by now, if only to reduce the number of threads on the topic.

I didn’t use that trait because it was broken, by any means. It just so happened to pair particularly well with my SymMed-Guard build, at the time. – of course it works well when its putting out too much damage lol

inb4 anyone else can try- can I have your stuff when you quit the game because of a disabled bugged skill?