Higanbana, FATEs, and Duty Finder - Fix this now

So I'm helping a friend with clearing Orbonne on AST and while we're waiting for the infinitely long queue time, I get on my SAM and do some FATEs while waiting. We pop, I disengage from the boss FATE and try to change jobs, but I cant, because my higanbana is on the boss. Not only that, but I just reapplied it. So now we miss the queue because of that stupid rule.

How is this still a thing?
I ran so far away that the boss wasnt even on my hate list anymore and it still wouldn't let me switch. Is there something more I could have done?

They really should've made it so that all active buffs/debuffs on an enemy are dispelled when it resets to prevent scenarios like this.

It's been a thing for the longest time in several other MMOs like WoW, so XIV lacking it is an oddity.

I wish they'd just change it so you can click "Yes" in the duty window regardless of job, and when you queue in, you're wearing whatever gear you were when you queued.

No more needing to panic run-away from a FATE to it a queue. I had this problem recently with my chocobo, since it kept trying to go back to hit stuff. Barely made the queue at 4 seconds remaining.

Quote:

---

Originally Posted by KageTokage

It's been a thing for the longest time in several other MMOs like WoW, so XIV lacking it is an oddity.

---

Isn't that kind of our trademark trend, though? Neglecting to make things with basic QoL considerations that may have rare but significant impacts?

If you ask me, you shouldn't have to switch to the job you queued as in the first place, the game should do it automatically during the loading screen, if you somehow lost your gear and couldn't change, the game would withdraw you from the duty when you press accept, this is something I have advocated for from the very beginning of the game, and I see no reason why it couldn't be possible, apart from awkward coding. The game could snapshot your gear when you queue and when you accept it would switch to that during loading screen, would save so much headache.

I would just not use Higanbana if you're queued for something and need to switch jobs.

Combat coding is wonky, evidenced by them not being able to fix the Blue Mage experience exploit. I don't think it's unreasonable to just note this one example and avoid it.

Huh. You know, they could make Senai detonate higanbana. It'd give Kaeshi Higanbana use.

I never encountered this, but it is very likely because it is so rare for me to use a DoT outside party play. I'd be even less likely to use it if duoing FATEs with someone, when the kills will come even faster. Still though, it would seem this is an oversight by the devs that has a pretty significant impact. It definitely needs to be fixed, but in all honesty accepting a queue should take precedence over everything. Once it pops, we should just be able to accept it without having to do anything else. That'd be pretty sweet.