There is currently no automatic packaging tool for preparing match functions for upload. For more details on writing and building match functions, see the document referenced in the overview. This user guide does not detail the process of creating and building match functions, and the instructions from this point assume that the function has already been built and the function assembly (along with all assemblies required to run the function) are located in a single folder hierarchy. Before you upload the replacement function, ensure that you download any previous logs that you might need for future reference. For example, for the running function testfunc1, the output might look similar to the following code snippet:Īfter a function has been replaced, you can no longer access old logs. If there is at least one running instance, the overall function state is running, even if some other instances are in other states. The overall function state is an umbrella designation that might cover specific instances in other states. Terminated: Instance is deployed, but was terminated (for example, as a precursor to deploying an updated version, or due to an error that prevents restarting).Waiting: Instance is in the processing of deploying or starting.For each instance, the value is one from the following states: ![]() This is similar to the overall function status state. There are as many items in this array as there are instances of the match function that is running.Įach element of the instances array contains an object with the following properties: PropertyĬurrent state of the function instance. The state of each running instance of the function. Failed: Function attempted to deploy but failed, or was running but failed and cannot restartįor states that indicate an error, you can see more details by downloading the logs, if they are available.Running: Function is deployed and is running.Pending: Function is deployed and is in the process of starting.NotRunning: Function is deployed but is not currently running.The status JSON object contains the following properties: PropertyĬurrent overall state of the function. State and status of the match function and any running instances 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |