Matchmaker hosting providers

Integrate your preferred game server hosting provider using Cloud Code modules.

読み終わるまでの所要時間 2 分

最終更新 1日前

重要

Unity Matchmaker will support Multiplay Hosting until the deprecation date of March 31st, 2026. To aid your migration away from Multiplay Hosting, migration examples for alternative hosting providers are available. Matchmaker will continue to work with Relay and Distributed Authority after the Multiplay Hosting deprecation.

Matchmaker uses queues and pools to customize matchmaking in your game. When creating or editing pools, you can specify the following Match Hosting types:

Client: Select this option for peer-to-peer, client-hosting matches.
Cloud Code: Matchmaker uses Cloud Code modules to allocate game servers and coordinate matchmaking results.
Multiplay: Select this option to use Multiplay Hosting in backward compatibility mode.

Hosting with Cloud Code modules

You can integrate Matchmaker with most game server hosting providers using Cloud Code modules to allocate game servers and coordinate matchmaking results. Configure game hosting in Matchmaker with Cloud Code modules in the .mmq Matchmaker queue file. In the Unity Dashboard, or the .mmq file's Inspector window, set the following mandatory fields:

Module Name
Allocate Function Name
Poll Function Name

If editing the .mmq Matchmaker queue file directly, these fields are

moduleName

allocateFunctionName

pollFunctionName

, respectively. While most third-party hosting providers are compatible, Unity provides example Cloud Code modules to integrate the following alternative hosting providers:

注

The previous list isn't exhaustive. The approach mentioned here supports most hosting providers. If your provider isn't on this list, use the previous examples as a starting point to get started with your preferred hosting provider.

These modules demonstrate how to allocate game servers using the respective hosting provider's API, and how to integrate with Unity Matchmaker to pass the necessary matchmaking results to the allocated server. For more detailed instructions about how to deploy and use these modules in your project, refer to the README.md file of the example repository. To set up one of the previous modules:

Read the README.md file of the example repository.
Clone the GitHub repository.
Install and set up the UGS CLI for your project.
Follow the instructions of the relevant
```
CONFIGURATION.md
```
file.
Run
```
ugs deploy modules/<provider_name>
```
.

Backward compatibility with Multiplay Hosting

If your game uses Multiplay Hosting and you don't want to update your game client, you must set its matchmaking compliance to be backward compatible by using a Cloud Code module to override the Multiplay Hosting settings. In this mode, Matchmaker calls the configured Cloud Code module to allocate, but continues to assign tickets with a Multiplay Hosting assignment to be compatible with existing SDKs. To set matchmaking to be backward compatible with Multiplay Hosting:

In Matchmaker, create a pool, or edit an existing pool.
At the Hosting settings stage of the pool creation, select Hosting type > Multiplay Hosting (Deprecated).
Set the following fields:
- Module Name
- Allocate Endpoint
- Poll Endpoint

注

Setting the previous fields causes Matchmaker to ignore the earlier configuration fields of Fleet, Build configuration, and Default QoS Region.

After setting these fields, perform any allocation debugging through your Cloud Code module.

Additional resources

Unity Cloud Code documentation

ドキュメント

Development

User Acquisition

Monetization

産業