- Newest
- Most votes
- Most comments
I'm not sure what is causing this but I'm curious to hear what someone from the Game Tech team has to say about this because I am also interested in how GameLift/FlexMatch handles tickets with more than one player and with more players than one team could hold. So I just wanted to add on to this by asking a few questions:
- Does FlexMatch, by default, try to ensure that all the players in a ticket end up on the same team in a match?
- If not, can you make a matchmaking request involving multiple players in a way that would force FlexMatch to place those players on the same team in a match?
- If yes (to the first question), would tickets containing too many players (either more than what one team can hold or more than what the entire game can hold) be rejected automatically?
@REDACTEDUSER
You are trying to run an x vs x team matchmaking rule and you are seeing:
- If you provide all the players for the teams in a single ticket you don't get a match
- A ticket with some of the players for the match is also not matched with single players for other matches
Can I ask about your set-up?
- Do you have a single matchmaker with expansions ie 14 x 14 wait, then try 7x7 then try 4 x4 etc?
- Or do you have multiple matchmakers per mode?
Can you also provide matchmaking ticket ids, matchmaking config names etc that show the behaviour raised above?
I do know (from this thread) that: " If you have all of the players you want for both teams, FlexMatch won’t be able to put the teams together in the same match – you would need to just start your game session by creating it and the player sessions directly."
@REDACTEDUSER
- If you submit all the players for a team on a single ticket, then the matchmaker will find players for the other team. So I believe by default it should respect your existing team.
- I am unsure what happens when you submit a 'team' ticket with more players than the team can hold, I'll see if I can find out.
Hey I know this is an old topic but I'm having the same issues where if both teams are filled with enough players to start the match and placed into one ticket, the matchmaking ticket will be stuck in searching status.
I'm thinking it would be nice to have one workflow instead of having to handle this kind of specific case separately.
Are there any plans on adding support for this?
Solved my issue by splitting the lobby into two tickets. Then match those two tickets together using an attribute in the ruleset
Relevant content
- Accepted Answerasked 7 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago