Review the structure for specifying parameters when creating a backfill ticket.
Read time 2 minutesLast updated 2 days ago
Important
Unity Matchmaker currently supports Multiplay hosting, or a client-hosted solution provided by Unity, such as Relay and Distributed Authority. The team is working on extending support to third party hosting providers (including Multiplay by Rocket Science and others), and is aiming to deliver this support in advance of March 31st, 2026. Matchmaker will continue to work with Relay and Distributed Authority.
The IP address and port of the server creating the backfill (using the format ip:port). This property is used to assign the server the matchmaking tickets. Required field.
The ID of the match that this backfill ticket is targeting. The match ID is contained in the MatchmakingResults in the allocation payload. The allocation payload is retrieved by the game server from the payload proxy as described in the Multiplay Documentation.
The ID of the pool to create the backfill ticket in. Cannot be used if the
attributes
field is present. The MatchmakingResults in the allocation payload contains the pool ID of the match it was created in. The game server retrieves the allocation payload from the payload proxy.
A dictionary of attributes (number or string), indexed by the attribute name.
The attributes are compared against the corresponding filters defined in the matchmaking config and used to segment the ticket population into pools.
Example attributes include map, mode, platform, and build number. (Optional).