Why in the world did they change Jump > Mirage Dive?

[zeth07]

Most likely because of clipping. You'd accidentally hit mirage dive right after executing jump/high jump, delaying your next GCD and misaligning your whole rotation.

They quite literally made changes SPECIFICALLY for this very situation prior to the change occurring. That can't possibly be the reason why. Like it wasn't even that long ago.


I'd love to know where this player feedback is of people asking to revert this change.

EDIT:

- From 6.0 -> 6.1 = "Jump: Action now changes to Mirage Dive while under the effect of Mirage Dive Ready."
- To 6.1 > 6.11 = "When Jump changes to Mirage Dive, there will now be a small input delay to prevent the unintended execution of Mirage Dive."
- To 6.11 > 6.2 = "Jump: This action will no longer be replaced by Mirage Dive while under the effect of Dive Ready."

Like what in the world.....literally WHO

[Azuri]

They quite literally made changes SPECIFICALLY for this very situation prior to the change occurring. That can't possibly be the reason why. Like it wasn't even that long ago.

And in doing so introduced another problem. Double-weaving High Jump into Mirage Dive became the realm of people who live in the server room. And there are situations where such weave is desirable. Two separate buttons just don't have either of the issues. Neither are you going to accidentally mash a Mirage Dive, nor is your action hampered by intentional delay.

[Aco505]

And in doing so introduced another problem. Double-weaving High Jump into Mirage Dive became the realm of people who live in the server room. And there are situations where such weave is desirable. Two separate buttons just don't have either of the issues. Neither are you going to accidentally mash a Mirage Dive, nor is your action hampered by intentional delay.

Correct. As I posted in another thread...

Having them on the same button caused way more issues than solutions in several situations. Double-weaving HJ + MD became as tight as before the animation lock reduction, thus being impossible unless your ping is good.

We're just at the perfect spot: after the animation lock changes but before the MD change.

If anything, ask the devs to give you an option to toggle it so that you can put them in the same button if you want, but this change is certainly positive.

[LifeupOmega]

- To 6.1 > 6.11 = "When Jump changes to Mirage Dive, there will now be a small input delay to prevent the unintended execution of Mirage Dive."

And there's the problem. Because you could no longer double weave Jump into MD without clipping thanks to this needless delay. I'd rather have the extra button back than the clunkiness we've dealt with prior.