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

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?

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

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

Quote:

---

Originally Posted by Gokuhan

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.

Quote:

---

Originally Posted by 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

---

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

Quote:

---

Originally Posted by JustPlainLucas

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

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.

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

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

Quote:

---

Originally Posted by Ashelia_Ferron

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?

Quote:

---

Originally Posted by StouterTaru

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

---

I, personally do not think they shouldnt change it for the overworld so that you can change right after the mob dies.

I'm mostly just saying it isnt a problem and it only is one for the op because he is making it a problem

Quote:

---

Originally Posted by Zari

I'm mostly just saying it isnt a problem and it only is one for the op because he is making it a problem

---

I had similar issues back in the day when I was in queue as one job, and doing FATEs as another. The distance away you need to run to get off the hate list for a FATE boss is insane, followed by 5 seconds to be able to change jobs. And that's assuming you didn't aggro another mob while you were running halfway across the zone.

And it's simply asinine to think that you're still "in combat" when the mob is dead. How are you in combat when you're not fighting anymore? I get the part about recovery but that's easily fixable by delaying the recovery a few seconds. Quit excusing this. And I'm not asking for special exceptions. You fix something at its core, and there's no need for special exceptions. And don't tell me I had bad judgement when I STILL HAD TIME ON THE CLOCK.

Quote:

---

Originally Posted by 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

---

It was a hunting log. I can kill them with no threat to me, just that it takes a bit longer, especially if you're a tank.

....seriously dude? With your 'argument' I'm highly inclined to agree with others here. YOU made the issue for YOU. It isn't SE's problem. And boo hoo you would have missed out on ONE enemy for a hunting log. Would it have killed you to just leave it be, switch back, AND have time to to get into your instance you waited on for a bit?

Quote:

---

Originally Posted by Bacent

....seriously dude? With your 'argument' I'm highly inclined to agree with others here. YOU made the issue for YOU. It isn't SE's problem. And boo hoo you would have missed out on ONE enemy for a hunting log. Would it have killed you to just leave it be, switch back, AND have time to to get into your instance you waited on for a bit?

---

Why should have to run when I can - and did - kill it in time? AGAIN, the issue here is I'm unable to change jobs when the mob was dead. I had time left over to confirm, but I was denied the ability to change over. How can you not see that as being a problem? Where in what world is it acceptable to just stand there and watch time go by and not be able to do anything with it?

You're just a broken record now. You THINK it's an issue you can't do everything when you want to. People know how the DF works by this point, you should too.

And again, boo hoo you missed a duty because you decided to kill an overworld mob while UNDERLEVELED compared to it so it took you longer. Should have just left it alone and gotten into your duty. You would have wasted lets see.....as you put it '40 seconds' killing something, when you can kill overworld mobs at ANY TIME.

You're creating problems for yourself, and all you're doing is blaming SE for issues you caused.

This is entirely a player made problem. I know because I've done the same things or had a zone load take JUST that second too long and had to requeue. It happens to everyone. If I know my queue is going to be long I just go fishing or crafting in a city instead of risking a time out due to just being wrong footed by mobs on the wrong class. Or y'know. Avoid it by staying your chosen class for the queue.

I know how the DF has worked for three years. I knew the risk I was running when I fought the mob and it took me a second or two longer to kill than I thought, but it still doesn't excuse the fact that TECHNICALLY, you should not be inhibited to change jobs after a mob is dead. I created this thread to address an issue that needs improvement that not only I, but you and everyone else in this game would benefit from. The fact that you and just about everyone here DEFEND this error is incredibly frustrating. Attitudes like yours prevent things from becoming better.

Quote:

---

Originally Posted by KorraBelle

This is entirely a player made problem. I know because I've done the same things or had a zone load take JUST that second too long and had to requeue. It happens to everyone. If I know my queue is going to be long I just go fishing or crafting in a city instead of risking a time out due to just being wrong footed by mobs on the wrong class. Or y'know. Avoid it by staying your chosen class for the queue.

---

And because it happens to everyone doesn't mean it needs to keep happening to everyone.

While it is annoying that there's a very small delay (nowhere near 5 seconds) after killing a mob before you can change jobs, there's simply no reason to spend time and money 'fixing' this. If your queue pops make accepting it your first priority. Problem solved. Get back to killing that weak pathetic over world mob when you get back from your dungeon or whatever.

Sure I've been in the situation of trying to gather red scrip materials while a timer is counting or finishing up a FATE or something else, but it's on you to determine whether or not you can beat the clock. What if you had missed an attack? Would you then be complaining that the timer should be 50 seconds instead of 45? They give you plenty of time and the only legitimate instances where it might be difficult to hit accept are when you inadvertently stumble into a cut scene (in a quest or something where you didn't expect one or you expected a much longer queue time).

Quote:

---

Originally Posted by JustPlainLucas

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

---

Broken, or works as designed. Who knows, who cares...

I live with the system in place, and i miss about 1 queue of 1000 to this...

so, I dont feel like it´s broken...