SocketWeaver needs to validate a client's API_KEY before the client can use SocketWeaver services.
You can use the CheckIn() method of the NetworkClient class to submit Clients API_KEY to SocketWeaver. The CheckIn() method also submits a client's PlayerId to SocketWeaver. The PlayerId is used in the Lobby servers and game servers to identify a player.
SWNetwork SDK randomly generates a unique PlayerId on the first launch of a game and stores the PlayerId on the device hard drive. NetworkClient loads the PlayerId from the hard drive in the Awake() method.
Using generated PlayerId
If you call CheckIn() without a custom PlayerId, NetworkClient uses the randomly generated unique PlayerId to check into the SocketWeaver services.
You can use custom player Id to override the generated playerId by calling CheckIn(customPlayerId). This is useful if you use service like Google Firebase to manage user profiles. You can use it for development testing as well.
Connect to Lobby Servers
After validating clients' API_KEY, SocketWeaver routes clients to a lobby cluster that are geographically closest to them. SWNetwork SDK will automatically connect to the assigned lobby clusters.