Guild Wars 2

Can’t use the 2nd part of the skill after dodging.

Can anyone confirm?

Hmm, something is wrong I think.

It has failed too many times even when the clone is alive – and yes after dodging.

Can anyone else confirm, or are we missing something? Seems like a bug.

Edit: weird, it works on the target golems after dodging, but has failed a number of times in combat.

Failed with me too. Honestly, I’d rather have iLeap/Swap merged and working as an “inverse” Phase Retreat, you teleport to the target and leave a clone where you were.

So I guess I have to play staff for now?

Exciton.8942:

So I guess I have to play staff for now?

Yeah.

Did they break it again =/

@Zmodd, then you loose the stun break which is pretty sweet. Or make the whole skill a stun break which will make it way easier to use (although they would need to reduce the casting time to instant, which they won’t do)

it seems a bit wonky, like as if when people dodge the phantasm, you cannot activate the swap.

Silverkey.2078:

@Zmodd, then you loose the stun break which is pretty sweet. Or make the whole skill a stun break which will make it way easier to use (although they would need to reduce the casting time to instant, which they won’t do)

Exactly, merge Illusionary Leap with Swap.

This seems to imply that iLeap was ever fixed since 3 years ago?! Man I must have missed the big event

I think I’m going to cry now…

Seems there is a delay when you shoot the clone out. Cannot swap instantly how we are used to. This lets the entity move away so the immobilize not work.

Just to cement this – swap is pretty kittened right now – randomly doesen’t work too often.

I feel like I’m playing mainhand sword with one skill and one auto attack…

Might have to use scepter until this is fixed.

Dawdler.8521:

This seems to imply that iLeap was ever fixed since 3 years ago?! Man I must have missed the big event

Yeah, it was working pretty well since they changed the clone spawn to be next to the target.

No problem here I find it works when you wait for the evades, it would be a bit unfair otherwise. I can’t say that I have experienced similarly with that bug.

Right I think I see my problem – I’m trying to dodge immediately after casting ileap, but because the cast time has been increased it means no clone – the skill goes on full cooldown and nothing to swap to. :/

Tbh I preferred the older faster cast time when I could dodge very quickly after casting. You have to wait a moment after casting to ensure the clone is summoned before dodging otherwise it doesn’t summon and you can’t swap.

A bit disappointing because it’s not as fluid as it used to be.

I’ve created a thread on the bug report forum, please go +1 it and add your diagnosis
https://forum-en.gw2archive.eu/forum/support/bugs/Illusionary-leap-fails-randomly/first#post5196926

Curunen.8729:

Right I think I see my problem – I’m trying to dodge immediately after casting ileap, but because the cast time has been increased it means no clone – the skill goes on full cooldown and nothing to swap to. :/

Tbh I preferred the older faster cast time when I could dodge very quickly after casting. You have to wait a moment after casting to ensure the clone is summoned before dodging otherwise it doesn’t summon and you can’t swap.

A bit disappointing because it’s not as fluid as it used to be.

I don’t think that’s it. I’ve had the clone spawn, hit the enemy, and was still unable to swap.

Not sure it’s a bug. The speed has been altered. The clone doesn’t appear at target instantly. We have to get used to a slight timing issue.

Edit. The clone appears but we are unable to swap immediately like before.

Exciton.8942:

Dawdler.8521:

This seems to imply that iLeap was ever fixed since 3 years ago?! Man I must have missed the big event

Yeah, it was working pretty well since they changed the clone spawn to be next to the target.

No it wasnt, the new insta-spawn just broke it in a different way than the run-to-target, it was still unreliable as all kitten -_-

Imagine if hitting 3 just teleported you to the target and immo them while leaving a clone at your original position instead… iLeap fixed to work just like the Thief shadowshot. But nooooooooo… Anet just had to come up with another unreliable broken teleport unique to the Mesmer because reasons. Just so they can get the opportunity to break it further, I guess?

Well I spent most of the time earlier this evening trying to get the hang of this casting delay for ileap and it still doesn’t flow nicely.

I’ll just have to continue to play with it another day and hopefully get used to it.

I think a quality of life change would be to NOT put the skill on full cooldown if you interrupt the cast early by dodging too soon and the clone isn’t summoned.

GJ Anet.

/15brokenchar

Robert said he increased the delay before a clone appeared from iLeap to give players a bit of a “fudge” factor so that players would have a better chance of being in range of their target to use the skill. I didn’t agree with this idea/logic when he mentioned it and after playing with it the other day, still disagree with it.

The problem people had in finding the proper range to use iLeap was mainly due to a lack of experience using the skill. The “problem” would have eventually solved itself on its own (from increased player experience) since there was no bug with the actual skill as far as I know.

Adding a delay to iLeap to help inexperienced players is flawed/bad for several reasons:

1) It assumes the target is stationary and you are moving towards the target as this is really the only situation in which it might help a newer player in using iLeap. If the target is moving away from you at a faster rate than you are moving towards it or if you and your target are both moving towards each other, adding this delay does not help and in fact makes it harder to use the skill successfully/optimally.

2) Adding a delay prevents players from immediately dodging after using the skill which is something a lot of players do. (For example, drop clone on target, dodge away to avoid hits, and use leap to get back on target/break stun.) Before the change, it was a calculated risk as to whether or not you should use a dodge immediately or try and get an iLeap clone out before using your dodge. It was a fine balance and the fluidity of the skill has changed for the worse in my opinion.

3) Adding delays to any range skilled to help people having a hard time finding the correct range is just a bad/flawed idea. If this is the reason for adding a delay to iLeap, why not add delays to every other ranged ability?

TLDR; Adding delay for clone was never something we needed and makes the skill worse.

Leodon.1564:

Robert said he increased the delay before a clone appeared from iLeap to give players a bit of a “fudge” factor so that players would have a better chance of being in range of their target to use the skill. I didn’t agree with this idea/logic when he mentioned it and after playing with it the other day, still disagree with it.

The problem people had in finding the proper range to use iLeap was mainly due to a lack of experience using the skill. The “problem” would have eventually solved itself on its own (from increased player experience) since there was no bug with the actual skill as far as I know.

Adding a delay to iLeap to help inexperienced players is flawed/bad for several reasons:

1) It assumes the target is stationary and you are moving towards the target as this is really the only situation in which it might help a newer player in using iLeap. If the target is moving away from you at a faster rate than you are moving towards it or if you and your target are both moving towards each other, adding this delay does not help and in fact makes it harder to use the skill successfully/optimally.

2) Adding a delay prevents players from immediately dodging after using the skill which is something a lot of players do. (For example, drop clone on target, dodge away to avoid hits, and use leap to get back on target/break stun.) Before the change, it was a calculated risk as to whether or not you should use a dodge immediately or try and get an iLeap clone out before using your dodge. It was a fine balance and the fluidity of the skill has changed for the worse in my opinion.

3) Adding delays to any range skilled to help people having a hard time finding the correct range is just a bad/flawed idea. If this is the reason for adding a delay to iLeap, why not add delays to every other ranged ability?

TLDR; Adding delay for clone was never something we needed and makes the skill worse.

I agree with this 100%.

Unfortunately I find the new ileap worse than the old ileap – the faster clone summon was better.

Zmodd.5427:

Silverkey.2078:

@Zmodd, then you loose the stun break which is pretty sweet. Or make the whole skill a stun break which will make it way easier to use (although they would need to reduce the casting time to instant, which they won’t do)

Exactly, merge Illusionary Leap with Swap.

I think you guys are suggesting this change because you are seeing just the benefits of offensively using an iLeap > Blurred Frenzy combo but to make this change would be a nerf to the skill to me and others who use the skill for both offense and defense. Defensively, you can drop an iLeap clone on a melee target (warrior/thief), dodge away/kite to bait gap closing abilities/stuns, and then use swap to juke your target. This is an important ability I use to mitigate melee damage and to make this change would drastically reduce my survivability.

With the way iLeap works right now, you can also use it to get away from another person while fighting near a cliff. Drop clone on target, jump down cliff and wait for your target to jump down also, then swap/teleport back up the cliff.

Leodon.1564:

Zmodd.5427:

Silverkey.2078:

@Zmodd, then you loose the stun break which is pretty sweet. Or make the whole skill a stun break which will make it way easier to use (although they would need to reduce the casting time to instant, which they won’t do)

Exactly, merge Illusionary Leap with Swap.

I think you guys are suggesting this change because you are seeing just the benefits of offensively using an iLeap > Blurred Frenzy combo but to make this change would be a nerf to the skill to me and others who use the skill for both offense and defense. Defensively, you can drop an iLeap clone on a melee target (warrior/thief), dodge away/kite to bait gap closing abilities/stuns, and then use swap to juke your target. This is an important ability I use to mitigate melee damage and to make this change would drastically reduce my survivability.

With the way iLeap works right now, you can also use it to get away from another person while fighting near a cliff. Drop clone on target, jump down cliff and wait for your target to jump down also, then swap/teleport back up the cliff.

It also works UP ledges. Just the smaller ledges. For example, on the mid point on Forest of Niflhel, if a ranger is on the ledges overlooking the point, you can use sword to spawn a clone and then “swap” with the clone to get into his face. Works on the lower ledges at midpoint on the Foefire map as well.

It’s kinda weird that Ileap in theory has the same basic function mechanic as heart seeker. Witch is Teleporting from one point directly to a target. No matter what movement that target has. Only the visual effects & damage are different. Why ileap does not work as well a HS?

Vieux P.1238:

It’s kinda weird that Ileap in theory has the same basic function mechanic as heart seeker. Witch is Teleporting from one point directly to a target. No matter what movement that target has. Only the visual effects & damage are different. Why ileap does not work as well a HS?

Because if clone is destroyed or doesn’t land properly=no teleport. Not to mention it doesn’t even damage.

Signed. Pressed leap clone appears, pressed again to swap, I doesn’t go through, so I need to press 1-2 times to swap places with my clone.

This skill has been broken or ridiculous since launch in wish anet would just replace it with something completely different. Give us a projectile that creates a clone on hit

This swap is an annoying piece of kitten. It’s failed on me numerous times today.

Leodon.1564:

Zmodd.5427:

Silverkey.2078:

@Zmodd, then you loose the stun break which is pretty sweet. Or make the whole skill a stun break which will make it way easier to use (although they would need to reduce the casting time to instant, which they won’t do)

Exactly, merge Illusionary Leap with Swap.

I think you guys are suggesting this change because you are seeing just the benefits of offensively using an iLeap > Blurred Frenzy combo but to make this change would be a nerf to the skill to me and others who use the skill for both offense and defense. Defensively, you can drop an iLeap clone on a melee target (warrior/thief), dodge away/kite to bait gap closing abilities/stuns, and then use swap to juke your target. This is an important ability I use to mitigate melee damage and to make this change would drastically reduce my survivability.

With the way iLeap works right now, you can also use it to get away from another person while fighting near a cliff. Drop clone on target, jump down cliff and wait for your target to jump down also, then swap/teleport back up the cliff.

Absolutely – I love the skillful juking that can be done even after they needed swap to not work without the clone, so I’d want to keep ileap as it is – summon clone on target and then swap to target.

But their explanation for adding the small time delay on summoning a clone is… well I don’t see the point. It was so much easier and more fluid to use before the patch – I don’t know where this whole business of “running to your target and failing to summon a clone” came from that made them add this delay but I definitely find it had made ileap even worse.

So while I appreciate the intention was good, please revert ileap to a faster clone summon. Honestly I don’t care if the clone attacks faster – the whole point is getting the clone out as quickly as possible allowing you to immediately dodge afterwards or something without breaking swap.

Just felt the need to feedback how annoying this clone summon delay is.

I fought against a MtD mesmer who was using scepter/torch and staff, and I was using sword/torch and staff.

iLeap failing nearly got me killed several times and the pathetic damage pressure when not using scepter meant I was at a huge disadvantage. I relied on shatters for the conditions because sword/torch is mostly utility and defence – but it’s just utterly pathetic how bad the damage is when relying on shatters and ileap/swap compared to before the patch.

I guess there is only one solution – go scepter or go home.

I honestly feel like putting the game down until something is done as a quality of life fix for this delay breaking swap after immediate dodge, as well as mtd of course.

It needs maybe to stick on target no matter what & not die until you leap. Idk..??!!