The output is a JSON object that contains the following properties: Propertyīase64-encoded MD5 hash of the uploaded match function archiveĭate and time the match function archive was created (uploaded) in RFC 3339 formatĭate and time the match function was last uploaded (replaced) in RFC 3339 format Use the matchmaking function get command to get the current status of a deployed match function. The quickest way to get local configuration running is to get your project ID and then run the following command:Īfter you delete the match function and archive file, the command responds with the message "deleted".
Accordingly, to get authenticated, you must set a project ID. This authorization happens against a specific project ID. Initializing configuration #Īll of the endpoints that matchmaking commands hit require auth to access. For information on calling the REST endpoints directly, see Matchmaker beta API Documentation. Developers can also directly use the REST interface. Internally, the CLI uses the REST endpoints that are provided by the matchmaking service. For information on configuring matchmaking logic, see Matchmaking How-To and Matchmaking-Logic Tutorial. This guide assumes familiarity with matchmaking logic configuration, and instead focuses on how to run and manage the configuration files through the CLI. The Unity Cloud command-line interface (CLI), mmbeta, is a tool for managing and operating Multiplay matchmaking.
The download link has moved to the downloads page Overview # If you are using Matchmaker Self Serve though UDash, please use the documentation here.
0 kommentar(er)
