Incendiary Bonds

Hi

I logged on today and received the latest update, since then I have found that Incendiary Bonds seems to be messed up.

It no longer does the initial fire damage to any monster I try it on.

Example if I cast IB on a lvl 12 mergoyle after the 3 seconds it does approx 34 damage, before the update it used to do 130 ish damage(cant remember exact figure) then approx 34 damage.

My IB description says 76 fire damage and set on fire for 3 sec.

Immolate says 47 fire damage and set on fire for 3 sec and is still doing the same 86 damage to a lvl 12 mergoyle.

A Guildy has tested it and it is the same for them, has Anet nerfed yet another Ele spell or is it a bug.

Anyone else found the same.

Regards Chanfron

Many Ele fans have noticed the bug.

First, are you both the same level? And what is your level compared to the mergoyle? You do significantly less damage with both attacks and spells against monsters higher level than you, and significantly more against weaker monsters. So if you are say level 8, and he is level 20, then your damage will be different from his.

If that isn't the problem, try doing /bug and report it.

Rico

don't use /bug , contact customer support

http://support.guildwars.com/





.

Hi and thanks for the replies, least I now know it is not just me.

I and my Guild friend are both lvl 20, I have 14 in fire and he has 16 but reduced to 14 for testing we both did 34/37 damage to a lvl12 mergoyle with IB.

Will report it to support.

Regards Chanfron

the update also messed up "diversion" it now does nothing.

Diversion: Energy Cost 10, Re-charge 20 sec.

"This skill does nothing."

Skill attribute "Nothingness"

Yeah I noticed something was wrong with diversion.

Well I got a responce to my support enquirery

*********
Thanks for contacting the Guild Wars customer support team with your
feedback. We always appreciate hearing from our players. The Guild Wars
development team is continually making changes to improve the game and
looks at your feedback very closely to make this happen.

Please note that in addition to writing us, you should always feel free
to post your constructive opinions/feedback/suggestions on any of the
numerous Guild Wars message board (http://www.guildwars.com/community/ default.html#forums), where your fellow players and the dev team will be
able to view them first hand. Thanks again!

Please feel free to contact the support team again if you encounter any
other problems.
*********

Though it does not realy tell me anything regarding the problem, I will go and test and see what happens.

Regards Chanfron

I'll have to test diversion now, because that realy would mess my mesmer up if it does nothing >_>
I can't test IB, but:
Has anyone else found any bugs?

Also, wasn't "/bug" stopped a long time ago?

I have tested Incendiary Bonds and it is still the same for me.

Since it was not mentioned in the game update log I will assume it is a bug and will continue the support enquirery.

Received another reply from support, this problem is a known issue and is being worked on by the development team so hopefully we will have a fix soon.

Regards Chanfron

does /bug not do anything any more?

When the Lorasu Windcasters use it on me it seems to work fine... I seem to recall hearing that diversion does not work particularly well in PvE, because monsters can somehow "cheat" around it. They may have multiple instances of the same spell, for example, so if you divert one of them, they can still cast the others fine. As far as I've seen, diversion works against players.

Rico

The /bug command is used for basic small bugs such as graphic glitches (since using /bug also sends the map, location, facing direction). You could send a /bug command saying *x* skill is buged but, considering all the players in Guild Wars, you can immagine the ammount of /bug incom the Devs get. Which means that these sorts of bugs are read, but it will take longer then sending it to the support.

If you have an important bug, I presume sending it to the Support Team is the best way to do it. Sending a /bug will also work, but might take more time to be read (if the bug is really important, theirs a fair ammount of chances that it will be fixed even before your /bug log is read ).