Guild Wars 2

Not sure if this skill (Torch 5 Bonfire) has always been like this, but since the patch I notice, that each burning tick does less damage, I recorded the burn 9 burn ticks displayed on a pvp golem.

556,500,445,389,333,278,222,166,111 = 3000 damage

In my case in PvP lobby, I have 914 Condi Damage:

According to wiki burning formula: (0.25 * Condi Dmg) + 328
So in my case: (0.25 * 914) = 228.5 + 328 = 556.5 damage per second (I’m guessing ANET round down)

So in this case, if someone stands in my bonfire field it is meant to apply 9 1 second ticks of burning. 9 * 556 = 5004 burn damage in total.

This means a loss of 2k damage from burn ticks on the fire field

The throw torch (skill 4), does constantly tick at 556 and is doing the correct damage.

Is this a bug, or a stealth nerf to fire fields? Does anyone know if it is happening on other fire fields?

Holy monkey…
… I came here to confirm. The Bonfire indeed is bugged.

But it’s not a slight bug at all. The damage difference is huge. Around 2K.
Also, the damage seems to refresh once it reaches the minimum and start from 445 again and keep getting reduced.

Anyways, other fire fields do not seem to be bugged. Elemental Ring of Fire ticked for constant 406 damage for the whole duration (different condi damage). Didn’t really bother trying out different ones since we know that Ranger is seemly the only one bugged.

This bug needs to be addressed ASAP.

Thanks for the confirmation. Yeah it’s big difference in damage especially when point holding in PvP. I have swapped my Torch out until it gets fixed.

Logged a bug posting in the support forums:
https://forum-en.gw2archive.eu/forum/support/bugs/Ranger-Torch-5-Skill-Bonfire-bugged/first#post4888090

While we are at it …
…
Poison damage from the Spider Application seems to go the exact same way.
It kept jumping from 84 – 47 … If I used my poison in addition to it (with condi damage) it started jumping from 148 – 84 – 67 – 59 – 34 – 14 …

And whichever way you look at it … It’s absurdly wrong.
Something needs to be done, and it’s a surprise that it’s only rangers (again) who need to be fixed. I’d really welcome being able to play the character that I played 90% of my PvP games with.

Another stellar patch…

I’ve noticed a lot of people saying condi damage is bugged in all sorts of weird ways. I’m playing SD engi until they sort things out.

If they can fix the eagle eye trait bug that gave us fury in record time, there’s no reason why they shouldn’t be able to fix this promptly.

Right now the bug seems to be just the opposite. the first tick is the ~600 dmg it should be, and the second to the last tick i get double the damage so ~1.2k per tick!

Hope this will be fixed soon, because ANet can be pretty slow with fixes sometimes.

On another note, just imagine how this update was bugged last week and also think how it would have been if it was released a week before…

I think it is a good signal. There are bugs with pet ai and condition damage. So i hope they’re working on both for a big update and they have accidentally released unfinished parts of it.

Aleksander Suburb.4287:

I think it is a good signal. There are bugs with pet ai and condition damage. So i hope they’re working on both for a big update and they have accidentally released unfinished parts of it.

I don’t know if i feel all too good about a burning condition with double damage :>

Edit: After a little bit of testing i think i figured how things work right now:
As soon as you increase burning duration (does not matter if it is %Condition Duration or %Burning duration) the Burn damage from Bonfire gets lower with every tick, and when you get no condition/burning duration at all the damage from bonfire will get basically doubled as you see it in the screenshot i posted before

Here are my tests (using bonfire), top one is against a target golem, and bottom against an NPC in WvW.

It seems the damage descends to a certain point then jumps back up to where it should be. Definitely bugged though.

EDIT: Flame trap is also bugged, torch is fine. Must be a fire field bug?

This is bound to be fixed soon because every class has this issue about burning right now. Tested out other classes and they all got burning ticking different numbers .

As i said, as soon as you add any +% Duration for burning the damage gets lower and jumps back, if you have 0% condition duration and 0% burning duration your burning ticks for 2 times the damage it should

Just want to confirm what Hepatolith said with another screenshot.

So yeah, definitely avoiding WvW for now.

What is this spaghetti code that seems to string the most random things together into breaking? :P

From what I heard, they were trying to make it so the fraction of a second left over on conditions would tick for some damage instead of just losing it all together. It would of been a good buff, or fix rather, for conditions if coded and implemented well. With this though conditions are a mess.

Condition classes that normally don’t trait into the duration line are at an advantage. Like a d/d ele will benefit from this but a guardian using Amplified Wrath is screwed. Sadly I use both Keen Edge and traveler runes (10% duration each). I’ll probably toss on speed runes and maybe Commanding Voice.