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

[Pigaxe]

So so sorry for my teribul spelling misstakes im in a rush to get to work and whanted to ask this question before i get going. FYI i have dyslexia.

This question might already be posted but i cant find it when i search for it(probebly due to my dyslexia). So if somone cold either point me to the right post or maybe explain it to me that wold be gratefull.

As the titel sais, Why can't we sign multiple classes to duty finder? I love to tank, heal and to dps and when i sign for duty finder i first pop dps then whidraw then tank then healer and see wich is fastes and hope for the best really that a quick dungeon will pop. it feals so much more sufisent if i cold just tick a box saying wich classes i whant to play and then just signup and let it be wichever one hapens to be best for the rest of the players signing. I think the duty finder que wold go down dramaticly or am i wrong?

Again sorry about the messy spelling and thanks!

[VenKitsune]

Small indie company please understand.

[Arrius]

Likely tied to the current job you have locked in when signing up.
Also, item level differences between different jobs can affect the queue, that's a additional technical hurdle they have to overcome.

[yukiiyuki]

We still can't move something in inventory while talking with npc or talk with NPC on mount. It's too difficult for them to implement, they made this game in a rush and from corpse of older game.

[Caitlinzulu]

Sounds like a nightmare to prioritise people.
Do you put a player that has selected healer or dps in one group as dps filling it or put it in the other forming group that needs a healer and a dps potentially saving it a lot of time waiting for another healer.

[Rasikko]

Well I think one way to go about this is to randomnize the roles you selected.

However...pretty sure tank and healer will come up 95% of the time.

[Valkyrie_Lenneth]

Small indie company please understand.

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.

[Jaelommiss]

Sounds like a nightmare to prioritise people.
Do you put a player that has selected healer or dps in one group as dps filling it or put it in the other forming group that needs a healer and a dps potentially saving it a lot of time waiting for another healer.

It's really not that hard to solve or design.

Implement a queue for each role. The first entry in each queue (first two dps) are assembled into a party. Each entry contains a player ID, class, and list of available duties. Each roulette would have its own trio of queues. All duties fall under one of the roulettes, so if you use DF to queue for a specific duty then you are entered in the role-specific queue for the roulette that that duty falls under. If you queue for multiple instances that fall under multiple roulettes then you are entered in multiple queues and the extra entries are removed when you are placed in a party.

Supposing a PLD who queues for Sastasha, Halitali, and Titania normal, an entry would be added to the leveling roulette tank queue (available instances: Sastahsa, Halitali) and the trials roulette tank queue (available instances: Titania). When one of those two entries reaches the front of their respective queue a party is formed using the first entries from the like-roulette healer and dps queues. Parties are formed around the entry in the shortest queue.

When the duty is accepted all additional entries for those players are removed from their queues.

The current system almost certainly works very similarly to what I just outlined.

Adding the ability to queue for multiple jobs is as simple as adding additional entries for the extra jobs when queuing and implementing a check to ensure that character ID for multiple members of the party do not match. Testing for character ID matches would be fairly simple. If two character IDs match, increment through the longest queue (most likely to have an entry for a different character) until a mismatch is found. If no one is found, increment through the other queue. This is very similar to solving for matching available duties. If both queues are somehow empty, then either assign the player as which ever role has the lowest throughput or wait until another person joins to assign them. If each roulette forms a single party at a time, then the current resolution method for deciding between two available parties (probably based on median queue times for the participants) can remain unchanged.


Unless I'm overlooking something this is all phenomenally simple programming. A first year computer science student would be able to create a program that does the same thing.

One of the hardest things would be assembling the list of available duties. That is based on item level when a players queues. One solution would be to use saved gear sets as options for queueing because those have an attached item level. The game would need to verify that the player has that set's gear in their armoury chest when they queue. This would work really well if they added an "equip this gearset" button to the duty acceptance window. A less appealing alternative would be to use a "save current class" option in the DF menu and to force the player to cycle through the classes they wish to queue as, though it's terrible UX.

[Fynlar]

I've wanted this for the longest time, not just to quicken my queue times, but everyone's.

[Hysterior]

I don't think you can create proper queues if everybody is registering as multiple jobs. We would have 0 visibility on timer.