Matchmaker hosting providers
Integrate your preferred game server hosting provider using Cloud Code modules.
読み終わるまでの所要時間 2 分最終更新 9時間前
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.
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 , , , respectively.
moduleNameallocateFunctionNamepollFunctionNameWhile 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 file.
CONFIGURATION.md - Run .
ugs deploy modules/<provider_name>