It's really useful post,[url=https://www.latestdatabase.com/]Buy Email Database[/url] thanks for sharing your information See more details....

And brainCloud 4.9 is live! Let us know if you have questions or issues! Paul.

You can bypass the peer dependencies by adding --legacy-peer-deps flag to your npm install. After modifying package.json, then use npm-install-peers to install the rest of peer dependencies.

Hi Jose, Sounds like you want to look into our Presence feature. Presence is designed to let users know when their friends are online. You can think of it like the old Xbox Live friends feature - where you can see which of your friends are online - and optionally what they are doing. And Presence uses RTT - so users will be notified in realtime when the presence information of a followed user changes. Presence works with Friends, Groups, and arbitrary lists of users. More details here - http://getbraincloud.com/apidocs/apiref/#capi-presence Hope that helps! Paul.

@JasonL Thank you!!

I figured it out. Segment has a Legacy - Project source type, using that worked.

I downloaded the BrianCloud plug in for Unreal Engine, I can integrate user authentication, and real-time chat between connected players in a day.

Solved: IDK if this is the right approach but I am using brainCloud's LitJson and JSONMapper. I will map out the things I need and put it into an object of variables I chose to parse out.

Update: Authentication seems to be going well. I can automatically sign user in using ANON, and attach an email and pass. I can also log a user in using existing email and pass and getAnonID and store it and proceed to use that AnonID to use AnonID on startup for silent authentication. However, if user selects anon account but then the user decides to log into an existing email and pass account, how would I go about deleting the new ANON account the user decides to "throw" away?

(Post the answer from brainCloud chat channel) Actually, there is a workaround that you can perform the tournament rewards adjustments, Turn off the auto claim Add a post-hook to Authenticate instead <- where auto-claim would normally run And in the post-hook look to see if they have tournament rewards, and if they do, claim them there - performing any award adjustments that need to be made.

(Note: this issue has been solved through our online chat support.)

Hi Reza, a simple workaround I would recommend is using our atomic methods, such as IncrementGlobalStats, to form the field values with the returned value of that method and some other characters you selected. (defined a global statistic ahead of time, call IncrementGlobalStats() get the returned current value of the global statistic, e.g. 123, then combine with the name you selected to a unique name, such as name_123)

@David-St-Louis-0 On my last question, can you restrict API calls to only be from a specific web domain or mobile app is? Google Api's allowed to restrict calls to firebase to be specifically from an web domain, or the specific app ID's. Another way to ask it, is there any way to restrict API calls to from a specific location? Thanks again, -Chad

Hi Chad, Sorry for the late reply. Yes, brainCloud can handle RPG style games well, it provides a rich set of features that benefits any type of game - includes very flexible multiplayer tech, Our built-in real-time multiplayer services are more based around the idea of shared game experiences that last a finite period of time (i.e. arena shooters, casual multiplayer, etc.). Our matchmaking, lobby services, room server system, etc are all geared toward making this sort of experience easy and inexpensive to build - but also can integrate with 3rd party or custom tech. brainCloud provides support for custom Room Servers that can support any type of custom or 3rd party multiplayer tech. For all these characters related data (user data), you can use User Entity or Custom Entity to store and trace them. The end-user profileId and anonymousId are stored securely in the client library wrapper on user devices. Users' IAP items and currency end up “unlocking” “awarding” these to the associated profileId, so that will never be lost. If a player is offline, you need to have some code on your side to handle this situation with the request callbacks, as long as “update()” is not called, it will not process sending packet bundles or process callbacks from the received packets. Shouldn't keep all calls for later. Instead, update player stats once connected, in 1 call. Hope that helps!