StandaloneMatchmakingConfigurationProps

class aws_cdk.aws_gamelift_alpha.StandaloneMatchmakingConfigurationProps(*, matchmaking_configuration_name, rule_set, acceptance_timeout=None, custom_event_data=None, description=None, notification_target=None, request_timeout=None, require_acceptance=None)

Bases: MatchmakingConfigurationProps

(experimental) Properties for a new standalone matchmaking configuration.

Parameters:

matchmaking_configuration_name (str) – (experimental) A unique identifier for the matchmaking configuration. This name is used to identify the configuration associated with a matchmaking request or ticket.
rule_set (IMatchmakingRuleSet) – (experimental) A matchmaking rule set to use with this configuration. A matchmaking configuration can only use rule sets that are defined in the same Region.
acceptance_timeout (Optional[Duration]) – (experimental) The length of time (in seconds) to wait for players to accept a proposed match, if acceptance is required. Default: 300 seconds
custom_event_data (Optional[str]) – (experimental) Information to add to all events related to the matchmaking configuration. Default: no custom data added to events
description (Optional[str]) – (experimental) A human-readable description of the matchmaking configuration. Default: no description is provided
notification_target (Optional[ITopic]) – (experimental) An SNS topic ARN that is set up to receive matchmaking notifications. Default: no notification target
request_timeout (Optional[Duration]) – (experimental) The maximum duration, that a matchmaking ticket can remain in process before timing out. Requests that fail due to timing out can be resubmitted as needed. Default: 300 seconds
require_acceptance (Optional[bool]) – (experimental) A flag that determines whether a match that was created with this configuration must be accepted by the matched players. With this option enabled, matchmaking tickets use the status REQUIRES_ACCEPTANCE to indicate when a completed potential match is waiting for player acceptance. Default: Acceptance is not required

Stability:

experimental

ExampleMetadata:

infused

Example:

# rule_set: gamelift.MatchmakingRuleSet


gamelift.StandaloneMatchmakingConfiguration(self, "StandaloneMatchmaking",
    matchmaking_configuration_name="test-standalone-config-name",
    rule_set=rule_set
)

Attributes

acceptance_timeout

(experimental) The length of time (in seconds) to wait for players to accept a proposed match, if acceptance is required.

Default:: 300 seconds
Stability:: experimental

custom_event_data

(experimental) Information to add to all events related to the matchmaking configuration.

Default:: no custom data added to events
Stability:: experimental

description

(experimental) A human-readable description of the matchmaking configuration.

Default:: no description is provided
Stability:: experimental

matchmaking_configuration_name

(experimental) A unique identifier for the matchmaking configuration.

This name is used to identify the configuration associated with a matchmaking request or ticket.

Stability:: experimental

notification_target

(experimental) An SNS topic ARN that is set up to receive matchmaking notifications.

Default:: no notification target
See:: https://docs.aws.amazon.com/gamelift/latest/flexmatchguide/match-notification.html
Stability:: experimental

request_timeout

(experimental) The maximum duration, that a matchmaking ticket can remain in process before timing out.

Requests that fail due to timing out can be resubmitted as needed.

Default:: 300 seconds
Stability:: experimental

require_acceptance

(experimental) A flag that determines whether a match that was created with this configuration must be accepted by the matched players.

With this option enabled, matchmaking tickets use the status REQUIRES_ACCEPTANCE to indicate when a completed potential match is waiting for player acceptance.

Default:: Acceptance is not required
Stability:: experimental

rule_set

(experimental) A matchmaking rule set to use with this configuration.

A matchmaking configuration can only use rule sets that are defined in the same Region.

Stability:: experimental