Ask a Question
Microservice Hooks
I want to implement a microservice and wonder if there are any hooks I can use when a player connects or disconnects to the Beamable backend so that I can reward player currencies based on the amount of time the user has been offline, like in a normal idle game.
How can I transfer player progress data from one realm to another?
I want to transfer player progress data (Stats, Inventory, etc.) from one realm to another. How can I transfer player data between realms?
Where can I put API keys and access them from MS code?
In the dashboard, is the "Realm Configuration" section where I could put API keys and access them from microservice code? Or would the API key have to be contained within the microservice itself? Or is there another solution on beamable for this?
Would this be done by putting it in a realm config? How do you access that via a service?
Could I use Beamable for several games?
Hello there!
Is there a way to flush data from leaderboards?
Is there a way to flush data from leaderboards?
How can I fetch more than 20 items in a given shop from the commerce service?
I am fetching items from the commerce service via a subscription:
_commerceService = _beamableAPI.CommerceService;
Why am I getting a CID/PID mismatch warning?
Why am I getting a warning about CID/PID mismatch when I go to build?
Using CloudSave in WebGL builds.
Since CloudSaveServices is basically backing up files specified in persistentDataPath on the backend is there a way to use it in WebGL builds since you can't save files in WebGL. Is there maybe an option to use CloudSaveService without local files and sending and loading the data from/to memory instead?
What to do if a PluginsHelper.CheckFileCollisions warning happens?
What should I do if there is a PluginsHelper.CheckFileCollisions warning in my project?
Why am I getting Exception: Invalid dependencies discovered for microservice?
My Microservice won't build. I am getting "Exception: Invalid dependencies discovered for microservice" when I try to build, followed by a "Build failed" message stating that no Dockerfile exists.