Set rules for large matches - Amazon GameLift Servers
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Set rules for large matches

Matchmaking for large matches relies primarily on the balancing strategy and latency batching optimizations. Most custom rules are not available. However, you can incorporate the following types of rules:

  • Rule that sets a hard limit on player latency. Use the latency rule type with the property maxLatency. See Latency rule reference. Here's an example that sets maximum player latency to 200 milliseconds:

    "rules": [{
        "name": "player-latency",
        "type": "latency",
        "maxLatency": 200
    }],

  • Rule to batch players based on closeness in a specified player attribute. This is different than defining a balancing attribute as part of the large-match algorithm, which focuses on building evenly matched teams. This rule batches matchmaking tickets based on similarity in the specified attribute values, such as beginner or expert skill, which tends to lead to matches players who are closely aligned on the specified attribute. Use the batchDistance rule type, identify a numerically-based attribute, and specify the widest range to allow. See Batch distance rule reference. Here's an example that calls for a match's players to be within one skill level of each other:

    "rules": [{
        "name": "batch-skill",
        "type": "batchDistance",
        "batchAttribute": "skill",
        "maxDistance": 1