Stuck WaitingForMatch when searching with lobby

Question

question

samcsantillo asked Sep 13, '19

Stuck WaitingForMatch when searching with lobby

Hey everybody, been having an issue specifically when matchmaking with multiple users on a ticket. When polling with players, I will initially get the WaitingForPlayers status, which is expected, but after that stage all lobby members will endlessly be in WaitingForMatch until the ticket cancels out. I am not too sure what I am missing and if there needs to be additional settings in the queue? Matching solo works fine for me too, and a bit confused cause from my understanding is the matching process should be the same from this point onward. Thanks!

Matchmaking

2

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

JayZuo ♦ commented · Sep 13, 2019 at 08:23 AM

Have you checked Multiple user ticket matchmaking? Follow this quickstart should help you.

0 ·

samcsantillo JayZuo ♦ commented · Sep 13, 2019 at 03:27 PM

Yes, I have read all that I can find. As mentioned, I am able to join the ticket just fine and get past the WaitingForPlayers portion of the ticket polling. The docs say everything after this point is the same as the solo queuing which works fine for me as well. All lobby members are endlessly polling the WaitingForMatch state until the ticket is cancelled however. I know there is something I am missing either in the queue or the player attributes.

0 ·

Answer 1 · 2019-09-16T09:43:13Z

Sarah Zhang answered Sep 16, '19

Could you provide your queue configures? So we can investigate it.

4

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

samcsantillo commented · Sep 18, 2019 at 04:38 PM

Sure thing, don't have any builds up so that is why that is blank at the moment. Not much going on there at the moment right now. I would think there is something else that is needed.

0 ·

1.png (44.2 KiB)

Sarah Zhang samcsantillo commented · Sep 19, 2019 at 08:39 AM

If you use the JoinMatchmakingTicket. It generally means you want to let the multiple players join one team. If you make multiple players JoinMatchmakingTicket successfully, they may share one ticket. The clients should keep their WaitingForMatch status. Only after the second ticket is created, the two tickets will be matched.

Do you want to make the Free for All match? I'm not very sure. If so, you can refer to this queue configure. If you want to do a 2v2 match, you can refer to this queue configure.

If you follow the sample queue. In your code, you don't have to add the MembersToMatchWith field and don't have to use the JoinMatchmakingTicket. You can use the code and the process like you matching the single-player. You just need to CreateMatchmakingTicket in your multiple clients, then GetMatchmakingTicket in your multiple clients. They will be Matched, then be assigned to the appropriate team. Please use the JoinMatchmakingTicket when you want to make specific players join one team.

In addition, we can't save the queue successfully when we check the Enable server allocation and leave the Build for multiplayer server blank. If it's blank we should uncheck this checkbox.

0 ·

samcsantillo Sarah Zhang commented · Sep 21, 2019 at 05:46 PM

Ah! Alright, that makes more sense. Apologies for any misunderstandings then, but one thing I am a bit confused about then is couldn't there be lobby members getting into different matches if that's the case? For example, if I need to match with somebody who has better ping in a different region or if a queue is filled with other players while there are still lobby members trying to join in on that one? In my case, the matchmaking is for a Free for All type of gamemode. Thanks for the clarification :)

0 ·

Show more comments

question