The Beamable Backend Provider gives you the option to interact with the Venly API using Beamable's Microservices.
Make sure that the Beamable SDK is installed inside your Unity project before switching to this provider! It is completely normal if you see multiple exceptions referring to Beamable when switching to the Beamable provider without the Beamable SDK being installed. You can either install the Beamable SDK or switch to another provider to fix these exceptions.
This provider uses Microservices to invoke Venly API calls through Beamable. To use the Beamable provider you'll have to configure some parts of the pipeline. So make sure you meet the following requirements before switching to the Beamable provider:
- Have the Beamable SDK installed and configured inside your Unity project
- Have an active Beamable account
Client authority (or Local authority) means the local client has authoritative control over a particular networked GameObject.
The steps below will guide you through the Beamable Provider configuration
- Install and Configure the Beamable SDK.
- Configure your Beamable Realm to incorporate Venly-specific keys
- Create a new Microservice (VenlyMicroservice)
- Configure the Microservice inside the Venly SDK Manager
- Provide the BeamContext object to the Beamable requester (optional)
Done, you can now invoke Venly API (Client Authoritative) calls!
It is of course also possible to use all the Venly SDK features inside any of your custom Microservices. More about Server Authoritative.
Server authority means that the server has authority over all GameObjects which do not represent players. For example, the server would manage control of all collectable items, moving platforms, NPCs - and any other parts of your game that players can interact and player GameObjects have authority on their owner’s client (meaning the client manages their behavior).
Updated 20 days ago