Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

Player

import type { Player } from "https://aws-api.deno.dev/v0.3/services/gamelift.ts?docs=full";

Represents a player in matchmaking. When starting a matchmaking request, a player has a player ID, attributes, and may have latency data. Team information is added after a match has been successfully completed.

interface Player {
LatencyInMs?: {
[key: string]: number | null | undefined;
} | null;
PlayerAttributes?: {
[key: string]: AttributeValue | null | undefined;
} | null;
PlayerId?: string | null;
Team?: string | null;
}

§Properties

§
LatencyInMs?: {
[key: string]: number | null | undefined;
} | null
[src]

A set of values, expressed in milliseconds, that indicates the amount of latency that a player experiences when connected to AWS Regions. If this property is present, FlexMatch considers placing the match only in Regions for which latency is reported.

If a matchmaker has a rule that evaluates player latency, players must report latency in order to be matched. If no latency is reported in this scenario, FlexMatch assumes that no Regions are available to the player and the ticket is not matchable.

§
PlayerAttributes?: {
[key: string]: AttributeValue | null | undefined;
} | null
[src]

A collection of key:value pairs containing player information for use in matchmaking. Player attribute keys must match the playerAttributes used in a matchmaking rule set. Example: "PlayerAttributes": {"skill": {"N": "23"}, "gameMode": {"S": "deathmatch"}}.

§
PlayerId?: string | null
[src]

A unique identifier for a player

§
Team?: string | null
[src]

Name of the team that the player is assigned to in a match. Team names are defined in a matchmaking rule set.