Illusionary Leap
It’s on the list of Mesmer bugs and to my knowledge has remained unfixed since the BWEs. The secondary effect on the skill involves a swap with the clone, and that swap often fails (usually when failure occurs it ports the player only a few feet forward, or nowhere at all).
It’s on the list of Mesmer bugs and to my knowledge has remained unfixed since the BWEs. The secondary effect on the skill involves a swap with the clone, and that swap often fails (usually when failure occurs it ports the player only a few feet forward, or nowhere at all).
If the clone created by iLeap dies, the swap point will be where the clone died. That might be what people failed to notice. I personally haven’t had any problems with iLeap.
no, the bug is the clone more often than not just doesnt spawn at all. regardless of range.
No fix for illusionary leap. No fix for signet of illusions. No fix for phantasmal haste.
Only nerfs.
I’m pretty sure they fixed it during the 10/1 patch when they made a bunch of fixes to illusions. I’m having it consistently create the illusion as long as I’m in range, and it’s creating it in situations where it used to fail.
The only problem I am aware of is that A. the range is a bit short so it is easy to screw up and cast too soon. This is less of a problem once you have more experience with the class and B. if there is a change in grade between you and your target the illusion doesn’t spawn at the target.
This is actually a pretty big issue for PvP and WvW. It annoys me enough that I won’t even use the sword in PvP but other people are so they must be compensating for it.
The problem with the range is that it looks like the range check for iLeap happens at the beginning of the cast bar not the end like iSwordsman for instance. When the range check was added to illusions in the BWE’s it was done in 2 stages the first was i believe undocumented and only affected phantasms, and the second documented change, which also added the “this ability requires a target” pop up to all illusion skills was added to clone spells like iLeap and obviously wasn’t implemented in the same way as the previous change
So trying to cast iLeap on the move, especially against a moving target can cause several issues with the clone spawning at maximum range.
Just add it to the list of inconsistent mechanics that ANet may or may not get round to fixing any time soon.