Why can't we sign multiple classes to duty finder?

[Makeda]

Sounds like a nightmare to prioritise people.

Other MMOs do it. Not all of them but some.

In WoW for example, if I have Druid, I can queue for all 3 roles. The first one needed pops.

In ESO, I think I can also do that, but need to reconfirm. And ESO was also rebuilt after launch in a super rush by a team even more budget constrained than SE...

At the least... it should queue by role and not by job.

Ideally it should let us switch jobs within role out of combat even in an instance.

- it should also let us accept and then do a job switch for us.
- and any cutscene you were in when accepting, should be restarted when you leave (or you just drop back to right before that scene).

[AnimaAnimus]

I would be happy just to be able to queue for multiple roulettes at the same time

[Moonlite]

Its almost like some things aren't related to how much money a company has, and are tied to either manpower deficiencies, backend problems from a darker time, or simply not enough interest.

But keep using your silly meme thing or w/e it is at this point.

Your examples are either something that could have been fixed with money given the amount of time this game has been out. Or they just don't care about QoL improvements. Man I hope they are just greedy and not that they just don't care. Both are bad but one feels so much worse to me.

[Nedkel]

I would be happy just to be able to queue for multiple roulettes at the same time

THIS.

Why its not a thing yet idk.

[DumdogsWorld]

Its almost like some things aren't related to how much money a company has, and are tied to either manpower deficiencies, backend problems from a darker time, or simply not enough interest.

But keep using your silly meme thing or w/e it is at this point.

If they really had no money, then it would be harder to blame them. There's little a company can do to force itself to grow.

But if they have a lot of money and are refusing to hire more manpower to treat manpower deficiencies, then that's completely on them.
(In which case, they deserve the criticism!)

[Tlamila]

At the least... it should queue by role and not by job.

Ideally it should let us switch jobs within role out of combat even in an instance.

- it should also let us accept and then do a job switch for us.
- and any cutscene you were in when accepting, should be restarted when you leave (or you just drop back to right before that scene).

When you queue, your level and ilvl are also taken into consideration, so queueing by role would make no sense as each of your jobs in that role is different.

[Valkyrie_Lenneth]

If they really had no money, then it would be harder to blame them. There's little a company can do to force itself to grow.

But if they have a lot of money and are refusing to hire more manpower to treat manpower deficiencies, then that's completely on them.
(In which case, they deserve the criticism!)

They aren't refusing to hire more people though, they are struggling to find people.

Also, in response to the earlier response, backend stuff is incredibly hard to change once it's been implemented at this level. They had to make the game compatible with old 1.x assets and that probably led to a lot of messed up Jerry rigged code to make systems talk to each other.

They'd likely have to halt patches for awhile to fix all the issues, but we already get complaint threads and backlash if stuff is delayed by a week or 2. There's no real feasible way to do this currently.

[DumdogsWorld]

They aren't refusing to hire more people though, they are struggling to find people.

Worldwide, there are programmers and people in other IT-related fields of work just sitting around twiddling their thumbs because it's difficult to find good work. Now people are saying that major game companies can't find enough people to work on their projects.

That's a big disconnect, no matter how you look at it. Somewhere out there, somebody just isn't trying. Whether it's just Square Enix or some worldwide problem, I can't say.

But if I'm expected to give sympathy to a company as big as Square Enix for using an engine infested with spaghetti code and unstaffing its development team, then sorry. No can do.

[Makeda]

When you queue, your level and ilvl are also taken into consideration, so queueing by role would make no sense as each of your jobs in that role is different.

Why?

Let's say someone has

WAR 31
DRK 53
PLD 47
GNB 80

They queue for 'tank' in the leveling roulette

2 DPS and a healer queue - let's just assume they're similar in levels

- the system looks at it all, finds that DPS #2 has the lowest 'queable level' as 'Archer 28'.
So we get thrown into Haukke Manor.

Everybody zones in, picks a job, and we go.

Conversely...

Queue for 'highest possible role leveling'

Turns out the healer has no healing job above level 71. But this was "leveling"... and it turns out that since the tank's GNB was 80, the system instead reads their highest non-max... DRK at 53. We get "Sohm Al".
Everybody zones in, picks a job, and we go. If the tank decides to use their GNB anyway - they get reward tokens for an 80, otherwise they get the leveling bonuses of a leveling toon.

IF we add a system to switch jobs out of combat - if the tank ever uses any non-80, the tokens are rewarded as a non-80... and the 'dungeon completion XP' / gil bonus could be spread out across the bosses but only given at the end.

This kind of simple math is what computers do really well at... :P

If you don't think they have the data to add all this up, read through your combat log sometime... it's insane how much is tracked.

[Moonlite]

They aren't refusing to hire more people though, they are struggling to find people.

Also, in response to the earlier response, backend stuff is incredibly hard to change once it's been implemented at this level. They had to make the game compatible with old 1.x assets and that probably led to a lot of messed up Jerry rigged code to make systems talk to each other.

They'd likely have to halt patches for awhile to fix all the issues, but we already get complaint threads and backlash if stuff is delayed by a week or 2. There's no real feasible way to do this currently.

In 2.0 I agreed with you, in 3.0 I wondered, in 4.0 I questioned, and in 5.0 it is obvious. You can honestly not believe by 5.0 they are struggling for staff. The team may be short staffed. They could have trained or poached enough staff by now. Some sort of disconnect between the company and the future employee's is happening. Money, workload, lack of ability to train, or whatever reason. The issue is clearly SE's fault and not the future workforce that you claim. I can not believe that this far into the games lifecycle. You honestly can't think it is the lack of employee's in the work pool by now?



The backend stuff is probably a mess from some 1.X stuff. I agree with you a 100%. Retainers and MB's are on my list of 1.X things that need to be fixed but the way they probably put them in over the course of 1.X it ain't happening.