StartMatchBackfillInput
import type { StartMatchBackfillInput } from "https://aws-api.deno.dev/v0.4/services/gamelift.ts?docs=full";
interface StartMatchBackfillInput {
ConfigurationName: string;
GameSessionArn?: string | null;
Players: Player[];
TicketId?: string | null;
}§Properties
§
ConfigurationName: string
[src]Name of the matchmaker to use for this request.
You can use either the configuration name or ARN value.
The ARN of the matchmaker that was used with the original game session is listed in the GameSession
object, MatchmakerData
property.
§
GameSessionArn?: string | null
[src]A unique identifier for the game session. Use the game session ID. When using FlexMatch as a standalone matchmaking solution, this parameter is not needed.
§
Match information on all players that are currently assigned to the game session. This information is used by the matchmaker to find new players and add them to the existing game.
You can include up to 199 Players
in a StartMatchBackfill
request.
- PlayerID, PlayerAttributes, Team -- This information is maintained in the
GameSession
object,MatchmakerData
property, for all players who are currently assigned to the game session. The matchmaker data is in JSON syntax, formatted as a string. For more details, see Match Data. The backfill request must specify the team membership for every player. Do not specify team if you are not using backfill. - LatencyInMs -- If the matchmaker uses player latency, include a latency value, in milliseconds, for the Region that the game session is currently in. Do not include latency values for any other Region.