Guild Wars 2

Did they change where the dagger 3’s burning speed ‘blast’ to the middle of the trail?

I swear pre-september patch, the blast was at the end of the trail, but now it’s in the middle.

it’s not just me right?

Yes, it defenitely changed a little bit. It’s not in the middle, more like at 85% of the path now. From my experience so far, it’s been easier to land the blast. Don’t know really why.. I didn’t even notice it straight away. Took me some games untill it tilted :p

Yeah, not quite the middle. I personally prefer it to happen at the end, visually, it’s easier to judge the end of your trail when closing the gap, then having to predict it 85% the trail.

I definitely threw off my distances in my attack chain when it got to burning speed part of the chain.

isit me or RTL overshots alot?

You sure its not due to some lag? I cant play the game this time but i had it even happen at the start sometimes nad it was all due to lag.Usually in spvp it worked when it happened to me and only got it in pve and wvw

Hmm I haven’t really noticed anything.

I find if your looking straight down and use burning speed, it shortens the trail to about 20% and the blast happens at the end. But in normal combat, you’re not going to change camera view every time your going to use burning speed.

But in normal over the shoulder view, and you use it, the blast happens a bit behind you after you finish the charge.

If you compare it to ele d/d videos pre september patch, you clearly see the blast happen at their feet.

@ jingkangtan.6752
RTL overshooting is pretty common, however the effect is less is you don’t hold down forward (w) towards the target. That being said sometimes this skill will miss a rabbit :/

Since the patch I have noticed it’s much harder (for me at least) to land Burning speed/lightning flash combo because of this slight distance change to the blast. Note: latency could also be a factor as I have been regularly teleported back to my original position after the lightning flash (a bit like how a thief’s shadow return operates).

Another observation is the immobilization bug occurring whilst doing burning retreat down a slopes and stairs (happened at various wvw/eotm keeps as well as Inquest Golem Mark II meta event).

Bumping this thread up, I want this fixed asap.

Upon further examination, I believe you are correct. The blast has been moved back definitely. It actually has helped me more than hurt me, but that’s just because I wasn’t aiming burning speed correctly, and when I do it still tends to hit. However, I’d still rather it be at the end. Just because that’s where it should be.

jingkangtan.6752:

isit me or RTL overshots alot?

RTL has been broken for over a year now.

The current implementation is so bad it frequently overshoots a stationary critter. The dev team appear to test only with local servers with single digit latency and so don’t realise how broken it really is with real-world latency.

@devs: try connecting to a euro or asian server from the US and then use RTL in WVW a dozen times and tell me how often you can hit your target. The implementation of RTL that shipped at release did not overshoot, it was introduced when RTL impl changed some months after release.

I just tried it in pvp, i didnt have a target, but the animation said enough, it was like 70% (the middle of the blast) of the fire trail. The outer blast circle (animation, maybe not in reality) didn’t even reach the end of the firetrail (just a few inches to short).

This feels pretty bugged and should be fixed asap please. I think it’s a byproduct of limiting the trail when ‘running against a wall’, nerf.

So it’s not just me

As I mentioned in previous post, I still believe it’s easier to hit someone when you know the blast is going to be at the end of the trail, rather then trying to distance yourself and predict the enemies position 70% into your trail as you pass through them.

@Phoebe, I think it is a byproduct of the recent nerf to the fire trails as well.

Perhaps a dev response would be fitting here?

devs don’t play or test ele, since they can’t play them at a decent level. plus, izzy hates eles and has so since gw1. he still lingers with the balance team and whispers "nerf ele, destroy ele" in their ears, while they’re apparently asleep at their job.

/ragemode off

i can’t remember the last dev response i’ve seen in here

edit: i just checked, it’s on page 20, 7 months ago and it’s an info post on CDI, not elementalist related.

Sorry for necro guys, however I think I figured out what causes this “effect” of premature blast occurence.

If I’m right, something was unintentionally changed with the skill, so the blast has a “fixed” location. In short, the blast position doesn’t count with swiftness (and maybe even with slowing effects like chill, cripple etc. however I haven’t tried that), so it always occurs in the location where it should if the character speed was normal (base), therefore swiftness causes the character movement to be longer, but the blast is in the same place as without swiftness. Does that make sense?

seems to be true for swiftness, chill and cripple etc. don’t have an impact. the trail is shorter and the blast is in fact at the right position.

tanztante.6532:

seems to be true for swiftness, chill and cripple etc. don’t have an impact. the trail is shorter and the blast is in fact at the right position.

Thanks for clarification, I couldn’t verify that, I’m at work atm.
However that means Anet unfortunately broken something associated with the skill while they were changing the burning trace of it (it wasn’t even needed imho, burning speed was not broken as FGS #4 was).