기술 자료

​
​

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분
최근 업데이트: 15일 전

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
법률 정보개인정보 처리방침쿠키Documentation Terms of Use개인 정보 판매 또는 공유 금지개인정보 보호 선택(쿠키 설정)

'Unity', Unity 로고 및 기타 Unity 상표는 미국 및 기타 지역 내 Unity Technologies 또는 그 계열사의 상표 또는 등록상표입니다(자세한 내용은 여기에서 확인하세요). 기타 명칭 또는 브랜드는 해당 소유자의 상표입니다.

일부 페이지는 편의를 위해 기계 번역되었으며 부정확한 내용이 있을 수 있습니다. 정보가 상충되는 경우, 영어 버전을 우선으로 참조하세요.


    이 페이지의 문제 보고