We need to be able to change jobs as soon as the mob dies

[JustPlainLucas]

I missed my que because I was stuck fighting on a different job and I had five seconds to confirm after I killed the mob and I STILL couldn't change over after that time. It has been like this for almost three years. Any and every action for that matter that requires the battle to end (Swiftsong for instance) needs to END when the mob DIES, not just fades away.

Don't you think it's time to fix this?

[Gokuhan]

Maybe next time run away from the mob and let return to it's place and de-aggro you. It's much quicker.

[Ashelia_Ferron]

The queue confirm time is 45 seconds. No mob on the overworld takes that long to kill.

If you're in the middle of a FATE or Hunt, just abandon it and get your queue

[JustPlainLucas]

Maybe next time run away from the mob and let return to it's place and de-aggro you. It's much quicker.

Oh yeah, I've tried to do that before, only to run into another mob and get aggroed so it's not always an option. Look man, don't bother replying to suggestions to fix broken things about games, because you aren't helping.

[JustPlainLucas]

The queue confirm time is 45 seconds. No mob on the overworld takes that long to kill.

If you're in the middle of a FATE or Hunt, just abandon it and get your queue

See my above reply. It baffles me that people defend SE when it comes to broken aspects of their games.

[Ashelia_Ferron]

See my above reply. It baffles me that people defend SE when it comes to broken aspects of their games.

Because your problem simply isn't a problem.

There is not a SINGLE place where you cannot outrun mobs in the time it takes to change and accept your queue. Not ONE. Even if you run into another mob, mobs do not have large range, they will chase for a bit and then go away. There is always open space somewhere. And again, if it's only one mob, and you can't kill it in 45 seconds, then you're just bad.

There's nothing broken about it, you're just complaining to complain because it's a non issue

[JustPlainLucas]

It IS a problem! Quit being dismissive, and quit assuming you know exactly what my situation is. For your information, the mob I was fighting was 5 levels higher than me, and I was WAR. So obviously, it wasn't going to go down quick. And I beat it in 40 seconds, which left me five seconds that I was unable to change to a job WITH THE ENEMY DEAD! There is NO REASON AT ALL that I shouldn't be able to change to a different job the MOMENT the mob is dead! I should NOT have to run away from something I can kill before my confirmation que is up. To try to defend SE on this shows a complacent and enabling attitude. I am not complaining just to complain. I am complaining to have an issue fixed.

[Zari]

You made your own problem
There is no real reason you should be fighting a mob that is 5 levels above you in the first place

[Ashelia_Ferron]

As the other poster said, you shouldn't be fighting something +5 levels.

And they can't change it anyway because they need combat to persist even if adds are dead.

Just look at A6S. Even if you kill one boss and haven't pulled the other, it keeps you "in combat" so that you can't recover quickly.

And no, they can't make "special exceptions" for each fight because that's way too much wasted development time for a problem that only YOU have because you can't use judgement to determine if you can get your queue in time

[StouterTaru]

And they can't change it anyway because they need combat to persist even if adds are dead.

Why do they need to restrict job change in combat (outside instances) at all though?