Unity Multiplayer Service Update - Release Notes July 9, 2015

We're happy to announce the Unity Multiplayer Service was updated today for code related to MatchMaker and Relay.



Unity Multiplayer Service Update - Release Notes July 9, 2015


Improvements

• Unity clients will now verify their application identity directly through the Cloud Project ID contained in the player settings, instead of fetching the AppID directly. This improves the flow significantly and fixes issues related to connecting to the MatchMaker from a standalone player. To use this feature Unity 5.1.1P3 is required. In Unity 5.2, beta 2 is required.
  
• Improve error messages for several errors
  
• Server performance improvements

Fixes

• Fix issues with DestroyMatch cleaning a match up properly when called
  
• Fix issue with refreshing app config
  
• Fix issues verifying a client’s Access Token for privileged commands, like DestroyMatch and DropConnection

Notes

• DestroyMatch is still not called directly from the Unity client, and matches will persist for 30 seconds after the last connected client has left. During this time ListMatch results will include these expiring matches. To force a match to clean up, please call DestroyMatch when the host is leaving the match.

 

My client send a message contains its nodeId to server, then the server call DropConnection, then I got this

System.FormatException: FAILURE Returned from server: DropConnection Failed unity_GetRelayHostInformationForNodeId for appId=

 

The error seems to indicate the client had already disconnected. If you stop talking to Relay the client will clean itself up automatically after 30 seconds, after which you'll get that error (I'm improving that error message in a future server release).

Is it possible the client already disconnected or do you see this with a client that's currently active on Relay server?

 

Synching data from lobby player to game player is broken.