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

[zeth07]

They literally just reverted a previous change which removed a button bloat, what is the logic for this?

There was a pretty clear intent for the change originally and it lasted this long, and I seriously don't think people were complaining about the other change.....

Now we just arbitrarily have one more button again....

[ShonenJumpBoy]

According to their patch notes and the reason, if you will believe it "Based on player feedback" I was pretty annoyed reading that because I agree, it made playing Dragoon at least for me, less bloated. I felt it was a more accessible experience to play Dragoon. And I embraced this change and thought it was a brilliant one at that.
Thinking about it a little more, I can see why some wouldn't want to constantly keep pressing the button when perhaps they don't wish to Mirage Dive at specific points and just use our base attacks.

But to me, The Devs wanted us to press fewer buttons and a majority didn't like fewer buttons so devs give more buttons back. Not really accurate but not far off lol.

[Rika007]

Honestly this was the one button bloat change they did that felt right. Why the heck would they go back on this over some of the other changes made to address button bloat that went over poorly?

Lets not even touch the Kaiten/Samurai feedback. I saw more negative posts about the adjustment of Pitch Perfect into WM then I saw about the MD change. This is just weird.

[ShonenJumpBoy]

Honestly this was the one button bloat change they did that felt right. Why the heck would they go back on this over some of the other changes made to address button bloat that went over poorly?

Lets not even touch the Kaiten/Samurai feedback. I saw more negative posts about the adjustment of Pitch Perfect into WM then I saw about the MD change. This is just weird.

How I imagine us asking...

Devs: Based on player feedback, we have changed Mirage Dive so it no longer overwrites Jump or High Jump on the hotbar when under the effect of Dive Ready. No need to thank us. We got you.
Us: Okay...Why?
Devs: Because...Player Feedback? They wanted it reverted
Us: Okay, Why?! That isn't an explanation! Tell us how their feedback convinced you it changed!
Devs: How their-...PLAYER FEEDBACK! THAT'S THE REASON!
Us: Aw crap!

No, I'm not kidding. That's their reasoning behind it all, I thought we were only ones affected by "Player Feedback" but the Astro also been affected by "Player Feedback"...but...Devs gave them a little something to ease their pain. https://na.finalfantasyxiv.com/jobgu.../#battleaction

[Engaru]

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.

[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.

[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.

[Payadopa]

I'm just happy about Lord and Lady. ;_;
But the DRG change I actually liked. Why they changed it back it beyond me.

[RyuuZero]

it's funny..
I had Mirage Dive after Jump written in a macro years before the change of 6.0
and I thought like "Hey.. I had that in a macro for years and now they made it official!?"
with that said.. I thought it looked so clunky that Jump becomes Mirage Dive, so yes, I like that they changed it back, BECAUSE: Mirage Dive is an active Button (just like Kaiten), which Jump not quite fit since you still have to commit to Jump, Mirage Dive is just an attack (which Kaiten is not!) that triggers Nastrond (btw, Geiskogul has the same cool down as Jump, so it lines up jump and thus can be performed alongside every Jump!)

I have the feeling that Mirage Dive will disappear in 7.0 so that Jump (itself) may trigger Nastrond

I was happy that I had Mirage Dive on a seperate button in 6.0 ^^ since that changed nothing for me^^