Guild Wars 2

The following bugs must be fixed first.

.

1. The +Condition Duration stat does not affect Illusions.

This is particularly devastating in WvW, where people frequently eat -40% Condition Duration food which severely cripples Staff Clone damage (the 1s Burning is negated entirely), and since Illusions do not benefit from +Condition Duration you cannot negate this by eating +40% Condition Duration food.

This bug is also partially responsible for why Phantasmal Mage and Confusing Combatants are worthless: Master of Misdirection, and any +Condition Duration for that matter, have no effect on the Confusion they inflict.

+Boon Duration has the same problem, but that’s not directly relevant to Condition Mesmers.

.

2. Bleeding inflicted by Staff Clones’ Winds of Chaos lasts 5s, instead of 7s like the player’s Winds of Chaos.

Burning from Staff Clones deal more damage in one second than Bleeding deals in 5 seconds. That doesn’t make sense and given this inconsistency is highly unlikely to be a “balancing act”. Given how the tooltip on the player’s Winds of Chaos shows Bleeding to last for 5s when you take Chaotic Dampening, this is likely another case of Illusions being forgotten when the base skill was changed.

.

3. Illusionary Elasticity affects Trident Clones and Phantasmal Mage, but not Staff Clones.

Given that Illusionary Elasticity would double the output of Staff Clones I wonder if this was intended, but it is an undocumented inconsistency so I will assume it is a bug. One way or another though, if there is going to be inconsistencies in what traits affect then it should be documented.

.

4. Phantasmal Mage’s bounce logic is enemy-ally-ally-ally-…, instead of enemy-ally-enemy-ally-… like other bouncing attack-buffs.

Again I wonder if this is intended, though for what reason I cannot say… I think the Phantasmal Mage would actually be balanced if its bounce logic allows it to double-tap enemies. Again, more inconsistency than obvious bug.

.

5. Phantasmal Duelist is a 100% projectile finisher when you take Duelist’s Discipline.

As with 2., this looks like a case of a skill being changed without changing other skills based on it, in this case the Duelist’s Discipline version of Phantasmal Duelist. Allows Mesmers to get 8x Confusion through Ethereal Fields. Probably the only bug fix for Condition Mesmers that’s a nerf.

.

The most critical bug is of course 1. Before any balancing act is done to Condition Mesmers 1. absolutely must be fixed first because fixing it changes a lot. Please, fix this bug that has plagued Condition Mesmers since the beginning of Beta.

Generally speaking, you need to post this in the suggestions forums if you ever want a dev to see it.

Ross Biddle.2367:

Generally speaking, you need to post this in the suggestions forums if you ever want a dev to see it.

And your claim is based on…?

Seriously, the Devs won’t look at a thread unless it’s been on the boards long enough (or garnered enough outraged replies in a short amount of time). Posting such threads in the profession forums makes more sense as people who visit these forums are much more likely to be interested than random players in the Suggestion forums.

Posting to show support. All of the above mentioned “bugs” are legitimate and should be fixed or at least commented on whether they are bugs or intended.

After a post I just made in another thread I wish I would have thought to compile such great information. Great job!

Just confirmed that condition duration now is passed on to clones.

oZii.2864:

Just confirmed that condition duration now is passed on to clones.

God almighty you are right. And +Boon Duration works too. This is the best undocumented change ever. Unless it was documented and I’m just blind.

Phantasmal Mage is much more effective now, although still pretty weak compared to other Phantasms. Now if its bounce logic allows it to double-tap it might finally be on par (though it might still need a CD reduction).

If they fix the other ones too and do something about scepter #1, condition builds may actually become viable to some degree.

well it’s nice to see that they fixed this, but still feels like they wanna just throw us a little bone as they know they hurt condition mesmers really badly….well my point still stands and confusion was way over nerfed, but thanks for the little fix.

From an sPvP point of view there is no Confusion nerf, unless you’re talking about Blinding Befuddlement. To be perfectly fair Confusion was far too damaging in WvW against players. Having said that, Confusion could do with a small buff in sPvP, and therefore WvW, as well; but that’s not a bug and not part of this appeal.

Which confusion was hiting too hard in WvW?
The one in 1v1 or small scale fights when you just have to wait the big stacks coming from shatter disappeared? or the one coming from ethereal field combo in large scales fights? Because thats the only 2 ways a mesmer can stack a lot of confusion and 1 is countereable when the other comes from an another game mechanic than mesmer.
From a sPvP point of view there is no confusion build for mesmers also.

Eclipse.1567:

Which confusion was hiting too hard in WvW?
The one in 1v1 or small scale fights when you just have to wait the big stacks coming from shatter disappeared? or the one coming from ethereal field combo in large scales fights? Because thats the only 2 ways a mesmer can stack a lot of confusion and 1 is countereable when the other comes from an another game mechanic than mesmer.
From a sPvP point of view there is no confusion build for mesmers also.

Let’s be fair, even if you’re great at waiting out/cleansing Confusion sometimes you won’t be able to help taking one or two ticks of damage, which in PvE Confusion means something like 4000 – 8000 damage. There’s also things like (for Asura) Pain Inverter, Confusing Images (which granted is easy to dodge) and with the CondDuration fix iMage would actually be quite potent if they kept PvE Confusion. With enough Confusion application your opponent won’t be able to cleanse them all and will have to take damage/be forced to do nothing for a long time.

Also, I’ve built an sPvP Confusion build taking advantage of the CondDuration fix, and it actually works reasonably well. Confusion from Confusing Combatants stick around for a while, and iMage can keep 3 stacks on its target for a reasonable amount of time. Not to mention conventional Confusion sources last a long time with lots of CondDuration.

Eclipse.1567:

Which confusion was hiting too hard in WvW?
The one in 1v1 or small scale fights when you just have to wait the big stacks coming from shatter disappeared? or the one coming from ethereal field combo in large scales fights? Because thats the only 2 ways a mesmer can stack a lot of confusion and 1 is countereable when the other comes from an another game mechanic than mesmer.
From a sPvP point of view there is no confusion build for mesmers also.

I run confusion in sPvP it works out quite well especially when stacked 10-15 high… Most players down themselves quickly ones that run condi removal take a little bit more time but not much.

I do think however that Confusion in sPvP and WvW needs to be stronger: it’s the only way Condition Mesmers can apply any sort of burst, except it’s unreliable and even when it works is not that dangerous.

Anyways, Condition Mesmers are still quite subpar in terms of damage compared to other condition damage professions, so while the fixing of bug 1 is nice the rest do need to be looked at.

Embolism.8106:

Ross Biddle.2367:

Generally speaking, you need to post this in the suggestions forums if you ever want a dev to see it.

And your claim is based on…?

Seriously, the Devs won’t look at a thread unless it’s been on the boards long enough (or garnered enough outraged replies in a short amount of time). Posting such threads in the profession forums makes more sense as people who visit these forums are much more likely to be interested than random players in the Suggestion forums.

Err, but the people you want to interest is the devs, not random players. That said, I never said not to post it in the mesmer forums. Simply that, if you want your suggestion to reach dev ears, put it in the suggestions forum. Given THAT, in the past I’ve posted an idea it’s appropriate forum for discussion and also posted it in the suggestions forum, and linked the two.

As to the basis of my claim? Forum moderators have, in the past, suggested players post their suggestions in the suggestion forum. They’ve also appropriately moved threads there. All that aside, Anet does take suggestions from the suggestions forum. That’s their intention for the forum. Of course you’d have to take that on it’s face. I don’t have to.

Bump for viability .

Ross Biddle.2367:

Embolism.8106:

Ross Biddle.2367:

Generally speaking, you need to post this in the suggestions forums if you ever want a dev to see it.

And your claim is based on…?

Seriously, the Devs won’t look at a thread unless it’s been on the boards long enough (or garnered enough outraged replies in a short amount of time). Posting such threads in the profession forums makes more sense as people who visit these forums are much more likely to be interested than random players in the Suggestion forums.

Err, but the people you want to interest is the devs, not random players. That said, I never said not to post it in the mesmer forums. Simply that, if you want your suggestion to reach dev ears, put it in the suggestions forum. Given THAT, in the past I’ve posted an idea it’s appropriate forum for discussion and also posted it in the suggestions forum, and linked the two.

As to the basis of my claim? Forum moderators have, in the past, suggested players post their suggestions in the suggestion forum. They’ve also appropriately moved threads there. All that aside, Anet does take suggestions from the suggestions forum. That’s their intention for the forum. Of course you’d have to take that on it’s face. I don’t have to.

My point is that player support is a prerequisite for Dev attention, and a thread like this is highly unlikely to get player support in the Suggestions forum.

Besides, this is more of a bug fix thread, and given we have a bug fix sticky here (which sadly isn’t up to date) it seems like the Devs want them here.