Gamelift Flexmatch Queue Not responsive At Times

0

So I have a queue based matchmaking system where I am lowering the minimum players needed every couple of seconds. What I am noticing is, sometimes matchmaking takes too much time and then I might update the matchmaking configuration with the same ruleset and match might start quicky. And there will be more players than the least minimum set by me. Lets say if the ruleset has minimum 25 mentioned after 40sec, if I update the queue it might start the GAME quickly with 50 players which means there were more than the minimum players in the queue. Is this some issue faced in flexmatch? How can I resolve this issue? Right now, all players have the same skill value.

My sample ruleset is given below.

{ "name": "1vs1Matchmakingf", "ruleLanguageVersion": "1.0", "playerAttributes": [{ "name": "skill", "type": "number", "default": 10 }], "algorithm": { "strategy":"balanced", "balancedAttribute": "skill", "batchingPreference":"largestPopulation" }, "teams": [{ "maxPlayers": 55, "minPlayers": 50, "name": "1v1" }], "rules": [{ "name": "SimilarSkill", "type": "batchDistance", "batchAttribute": "skill", "maxDistance": 10 }], "expansions": [{ "target": "teams[1v1].minPlayers", "steps": [{ "waitTimeSeconds": 25, "value": 30 }, { "waitTimeSeconds": 45, "value": 15 }] }] }

1 Answer
0

Hello! Flexmatch matchmaking expansions can be designed to favor oldest vs newest tickets in the queue via the "expansionAgeSelection" rule set property - https://docs.aws.amazon.com/gamelift/latest/flexmatchguide/match-design-ruleset.html#match-rulesets-components-algorithm-expansion This can give you more consistent matchmaking timings, as your expansion rules will always be triggered by the oldest ticket in the queue.

AWS
answered 3 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions