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).

[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.

[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.

[Xtrasweettea]

[snip]

In order for this to work, all jobs that are unlocked and meet the minimal level for Satasha will be considered when measuring for dungeon queues for a specific role. It will always measure to the lowest level since you are queuing by role and not by a specific job.

That's great for people who have multiple jobs close to each other, it isn't great when you have a huge disparity in level.

Your example with the tank player is a good example of a player with level disparity. That player will never be able to do any dungeon above Haukke Manor since their WAR is level 31. In order to expand that player's choice of dungeons, that player has to level WAR... even if they hate the job and never wanted to touch it ever again.

The system cannot select a dungeon higher than Haukke Manor unless you (as the idea provider) wants to be with OK with a player not being able to choose a job they want to play. If that tank player gets Mt. Gulg, for example, they can only choose GNB. They cannot chose PLD nor DRK, system won't let them. Which negates the whole reason to queue role; that player basically ended up queuing as a job rather than as a role.

If you start excluding jobs you don't want to be considered in the algorithm, just to increase your chances of not getting dungeons you are capped at, you might as well have never bothered making queues by role in the first place.