文档

​
​

Development

User Acquisition

Monetization

工业

Multiplayer Services SDK

All Services

Multiplayer Services SDK

此页面不支持所选语言。
Multiplayer
​
​
Multiplayer Services SDK
  • Overview
  • Get started
  • Use multiplayer sessions
  • Manage sessions
  • Connect players through a relay
  • Networking
  • Matchmaking
    • Get started with matchmaking
      • Matchmaking ticket flow
      • Authentication
      • Matchmaking rate limits
      • Queues and pools
      • Matchmaker hosting providers
    • Manage and configure matchmaking
    • Matchmaker troubleshooting
    • Integrations with other UGS services
    • Deploy Matchmaker configurations
  • Monitor and debug sessions
  • Tutorials
  • Reference
  1. Multiplayer Services SDK

Matchmaker ticket flow

Understand how tickets move from creation through matching to server allocation.
阅读时间3 分钟
最后更新于 16 天前

When using Matchmaker with a game server hosting provider, you must use Cloud Code modules to allocate servers and coordinate matchmaking results. The following Matchmaker flow diagram takes you through the creation of a matchmaking ticket to the allocation of a server for the created match, and the ticket assignment.

Flow of a ticket from creation to allocation.

  1. When a player launches the game, the game client authenticates using the Unity Authentication Service.
  2. Once the player has selected their game parameters (such as game mode), the game client creates and sends a ticket to the Matchmaker service.
  3. Matchmaker matches the ticket with other players' tickets and requests a game server allocation from your preferred game server hosting service to host the match by calling the Cloud Code allocation function configured for that pool. If supported, the allocation can be passed information about the match made via matchmaking results.
  4. In the request to the Cloud Code polling function, Matchmaker passes the data returned by the allocation function to gather information about the allocation. The polling function can return one of three states:
    allocated
    ,
    pending
    , and
    error
    . If the polling function returns
    pending
    , Matchmaker repeatedly calls the polling function until it returns
    allocated
    or
    error
    . If
    error
    is returned, then Matchmaker assigns an error to all the tickets in that match.
  5. After the polling function returns
    allocated
    , the server starts. The server retrieves the matchmaking results from either a provider-specific endpoint, if supported, or the Matchmaker's matchmaking results endpoint to get the information on who the players are and their distribution across the different teams.
  6. Once the server is allocated, Matchmaker updates the tickets in the match with the connection information.
  7. The game client polls the Matchmaker service every second to get the ticket status. Once the server connection information is added to the ticket, the game client retrieves it, connects to the server, and joins the match.

Copyright © 2026 Unity Technologies
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择(Cookie 设置)

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标(此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见,一些页面是机器翻译的,可能包含不准确的内容。如有信息不一致的情况,以英文版本为准。


    报告此页面的问题