Auto-switch job on Duty entry ... I can't believe this isn't already implemented

If I had to estimate, I'd say about 99.999999999999999999999999999999999999999% of all times that I've missed a duty prompt has been because I've gotten stuck playing another job while I wait for the duty finder to pop. I do this due to the long wait times especially for DPS, which can vary between 10 and 50,000 minutes more or less.

Take today, for example, the most ridiculous one I've ever encountered. I was waiting for a DPS duty during which time I was going around killing level 50 elite marks just for the easy tomes. I was doing this with my level 100 WHM so clearly no threats involved. Well yay for me, I happened to be fighting some random lv50 elite that threw off a massive circle AOE, I stood in it thinking "what could it possibly do to my lv100" .. well it caused a 1 minute long petrify. Ridiculous and shortsighted that a mob was even designed to be able to do this in the open world but of course my unlucky scenario was, I couldn't move, I could suicide, I couldn't run. All I could do was watch my duty finder count down and eventually fail giving me a fail mark for the day.

I get it, there's no permanent issue here as the marks reset daily and odds are you won't encounter something like this 3 times in the same day, but it's still rather infuriating to have lost the 15 minutes spent in the queue. I can't believe this is still a thing years and years and years and years and years later :/ SE get on the ball and just fix these things already. Just allow us to accept entry to the duty even if we're on the wrong job and just switch our job automatically, how hard is that honestly.

That would cost them 20 million bucks to implement. its way too expensive.

I'm assuming they don't do this because of other sorts of edge cases, where someone signed up, and in the 26 minute wait for the DPS queue...somehow decided to desynth their dancer weapons and then they are not actually capable of auto-swapping into the job.

If they could get around that sort of thing, it would be a nice feature.

I just wish I can queue up with multiple classes. I have everything maxed out but I can only queue up for one thing with one character. I want to be able to queue up for multiple duties with any of my classes as long as the ilvl is met.

Quote:

---

Originally Posted by Astronis

I'm assuming they don't do this because of other sorts of edge cases, where someone signed up, and in the 26 minute wait for the DPS queue...somehow decided to desynth their dancer weapons and then they are not actually capable of auto-swapping into the job.

If they could get around that sort of thing, it would be a nice feature.

---

Presumably at least for this specific edge case, it's the person's own fault for desynthing their weapon while they're in a queue. Ok one could argue it was also my own fault for deciding to play some kind of open world content while I wait for the queue, but I think most reasonable people can see the difference. In this instance if the weapon is no longer available, the user can't join the duty and therefore gets a failed entry > strike. Honestly if someone is desynthing (or selling or through any other means losing) their weapon for the job that they duty-queued for, it's probably because they're actually trying to be destructive

Quote:

---

Originally Posted by Appleboops

Presumably at least for this specific edge case, it's the person's own fault for desynthing their weapon while they're in a queue.

---

Well...yeah. People do dumb stuff all the time. But it would prevent the auto-swap and the game system presumably isn't going to be programmed to know why a player can't swap for the queue, it's just going to try to swap the job and fail. If you want the game to kick people out of queue for that failure to swap, it would have kicked you out as well, because it would have occurred before the zone-in and the game detected an inability to swap jobs. It's not going to be programmed to see this person failed to swap jobs because they were in combat while this other person failed because they don't have a weapon. Otherwise, they would be auto-swapped in-instance and by then they can't be kicked out of queue and we may as well unlock the ability to swap jobs in-instance (I would like that, though it would cause all kinds of other issues!)

I'm not going to pretend to know how the game's engine works or how the different systems interact with one another and all that mess, that's SE's thing to sort out. That said, if/when you sell or desynth a weapon and then try to swap to the job that had that weapon, in the event you have a different weapon of the same type you do get a popup message asking if you'd like to update your gear set with the new weapon that is available. This suggests to me that at least the game has ways to check if the weapon is there or not, and really I don't see why there wouldn't be a way to do that. In any event, again I'm not here to get into the grit of the "how" but I'm more just here to say this should have been a feature right from the beginning and the fact that it's not makes me sad

I don't think you needed to take to the forums because you got jebaited by an overworld mob.

I don't think we need this system for the 1 time a decade you get put into a situation where you're unable to switch to another job for a full minute. It doesn't take that long to leave combat, finish a craft, etc. That's a lot of dev work, testing, implementation, QA, edge case discovery, and new system interactions that would need to be developed for no real gain or QOL.

Most normal people would laugh this off, hold the L, and leave with a funny story to tell. "Haha, I missed a queue because an ARR mob turned me into a statue for a full business day." You should be sad that you've chosen the negative route, op. Not sad that a video game doesn't have every single little corner padded to prevent one from bumping into the corner.

I personally don't think it's so rare a scenario as you're making it out to be, yes MY situation that I described was 1 in a gametime but there's a much more generic scenario of someone farming mobs in the open world for basically any reason and then getting queued and unable to swap jobs. Most mobs are aggro and it's happened on many occasions where I've been doing low-level grind while waiting for the queue, then it finally pops but the aggros are chasing me down. Choice one: hope to kill in time and swap jobs quick - Choice 2: try to run, but then in that scenario I've had times different aggros just keep tagging you and so long as anything's chasing you you're stuck. edit: I forgot to mention but if the Chocobo partner is out it's even worse sometimes because I've had times he runs off to go fight something god knows where and I get stuck "in battle" when I'm not actually in battle, or trying to run but the Chocobo stays behind XD so basically yea the partner Choco can make things messier sometimes here too

In any case, it doesn't help to over exagerate on either side of this coin, this was my experience and this was the reaction I had. Given that the wait time for queues is so drastically varying (sometimes it's 3 seconds, sometimes it's 20 minutes), given that the "estimate" that's shown is laughably wrong a lot of the time, and given that there's an actual penalty system for missing a queue, I feel that yes they should pad every scenario so that the Player is not the one suffering consequences for scenarios where they wanted to join properly but just couldn't simply due to an engine weakness or lack of design foresight

That said we are all privy to our beliefs and opinions on the situation, and I hold nothing against anyone who disagrees with me

Quote:

---

Originally Posted by Appleboops

snip for length

---

In the scenerio you described, low level mob aggro, you have a full minute to pop sprint and run a single direction away from the group of mobs you're around. Are you seriously trying to say that's unmanageable enough to the point where this is a consistent issue? There is like 1 overworld mob type that will actively draw you in if you run away, frogs, and they have a cool down on that ability.

It's 60 full seconds. Overworld mob aggro ranges aren't that massive. Crafting I could understand maybe running into the issue more often because those do take a bit of time and you're forced to leave the animation itself before you can change. But overworld mobs?

Brah.

I'm fact, come to think of it, the proposed system is actively harmful to crafters. If the queue pops, right now crafters have the choice of trying to finish, failing/forcing completion of the craft, or just letting the queue expire. With your system, if queue pops during a craft and you can't finish in 60 seconds, it's an auto-fail. It'd have to be, or else you could use the duty system as a safeguard to not fail the craft. The proposed system removes options from crafters who get caught at the beginning of an expert.

Like, nah. Just run away from the mob or fate when queue pops. 60 seconds is plenty of time.

Which is another point. Ya'll supporters of this wanting to make the 3, 7, or 23 people wait those 60 seconds just to try to kill a fate or mob before you're force switched to another job when going into instance? Because I know a ton of people would default to "the system will just accept for me, I don't have to hit the button" with this system. As if the wait to get into content isn't bad enough. We gotta wait that little bit longer to get in because someone decided to try to Yolo a fate before queue?

Nah. I was taking the piss earlier. I'm now actively against this suggestion.

Quote:

---

Originally Posted by IOwn92FCHouses

In the scenerio ... "snip".

---

This is entirely misled so I'm sorry if you misunderstood what I was actually proposing. I am not proposing that at the end of the 60 seconds you automatically get joined into the duty regardless of situation. I am only proposing that if you are on the wrong job when the duty timer pops, you can click to join right away without needing to swap jobs first

This system would not affect crafters at all. If you are crafting and you don't want to join the duty when it pops because you can't finish your craft in time, the timer would run out and you'd get a mark for failing to join
This system would not be exploitable or "lazy" because again, it would not auto-join you at the end of the 60 seconds. Hell, if that were the case people could AFK join which is a terrible situation.

This would [B]only mean[B] that if you were on a different job when the duty finder timer pops, you'd be able to click Join right away and not have to swap jobs, eliminating any scenario where if, for whatever reason, you could not
I'm not going to try and debate over scenarios or situations where you can try to run from overworld mobs or etc etc, I've personally been caught in situations where I'm struggling to get away from the mobs because as I try to run, another one picks me up and so on. This may seem unlikely to you but in my personal experience it has happened many times, which is why I'm here. The event I described in my OP was not a magical one-off that had me come here, it was a "last straw" situation because it had already happened or nearly happened enough times before.

I'd like to be able to click "commence" and it automatically switches me to whatever I queued as, so I don't have to thumb through 20-something gear sets when queue pops.

Quote:

---

Originally Posted by Shinku_Tachi

I'd like to be able to click "commence" and it automatically switches me to whatever I queued as, so I don't have to thumb through 20-something gear sets when queue pops.

---

This here is part of why I am looking forward to the new command whatsit they are adding soon. I have four whole hotbars dedicated to jobs so I can switch quickly, it's gonna be nice to stuff those all into one convenient location.

Sure, an autoswap would be nice too, just don't think it's something that would work with how the game is set up.