Guild Wars 2

I’m waiting around hoping this happens.. anyone know? :/

No., Anet has said it will never be fixed because it’s a terrain issue not a mesmer issue. (so they say.)

don’t they use that one for any issue on Mesmer they don’t want to fix

jportell.2197:

No., Anet has said it will never be fixed because it’s a terrain issue not a mesmer issue. (so they say.)

IL was a terrain issue. IE is just a lack of concern for mes.

IE on clone doesn’t have terrain issue lol

SteepledHat.1345:

jportell.2197:

No., Anet has said it will never be fixed because it’s a terrain issue not a mesmer issue. (so they say.)

IL was a terrain issue. IE is just a lack of concern for mes.

Oh kitten im a kitten . Lol just read another thread about iLeap then swap… Totally misread my bad! haha

Jesus Christmas you guys scared me. Never fixed…

I seriously want this fixed, it’s a build breaking bugg and with it sorted we will se a whole new breed of mesmers.

/Osicat

It will be nice to have it fixed, but I am worried that it might make staff clones a bit ridiculous. It would certainly make my current condi build extremely strong. Would be a nice buff for my shatter build though.

Probably not going to get fixed within the next year, lets be honest.

Ever? yes. Soon? what do you think lol. We’ve all seen Anet developing , fixing and polishing by now.

Well they blatantly lied to us about fixing it. Let’s face it, it won’t happen. They don’t care about mesmers anymore.

More like; they overcomplicated their codebase past the point of logic. Let’s face it, you’re dealing with two problems here:

1. ANet has displayed that they like the more roundabout way of doing things. Ferocity comes to mind, IMHO. Why create a “new” stat, when you could’ve altered the endpoint of the “old” stat, instead?
2. They’ve also shown an alarming disconnect between the original coders of each class, and the problems of each class. Do any of you think that the people handling -say- Mesmer or Ranger are the same people what originally designed either?

My guess is that they have tested it and feel that it would be too strong. I can’t see another good reason, considering the iMage gets an extra bounce. Why they can’t/won’t just admit that is another issue, though. I know we would all rather not have the uncertainty.

I’m thinking that Anet will never ‘fix’ it because in doing so it would be OP.

Then they should say that instead of saying they’re fixing it or ‘looking again’ at it.