Namespace QuickStart

Example of adding players to a user's ban list. This example shows BigScreen communicate with entity manager directly to add player to ban list. If actor also need this data, BigScreen should send a game message to actor. See example project for more in-depth sample.

BigScreen class represent the BigScreen application which create a session in Lobby Service.

After User behaviour has finish initializing AuthController, set this gameobject to active to create a session.

Client represent the client application (usually running on mobile device).

After BigScreen has finish creating a session, set this gameobject to active to start client connection.

This class shows usage of the EntityManager.

This class shows usage of the LeaderboardManager.

This class shows usage of the user management.

Always call !:AuthController.InitAsync first to intialize before access to rest of the platform. This also restored user from playerpref which may be registered or guest user. Use !:AuthController.LoginStatusChanged to see the login result.

A login user is a registered timeplay account. A logout user is a guest user, which has restricted access but still has some access to the platform.

Actor is part of the game which host logic specific to a game. ActorNetworkID defines messages for bigscreen and client to communicate with the actor. Below are messages for the example showdown actor.