Forum wide moderators
Hi @tlim and @devsleeper ,
Player stats are definitely useful for keeping all-time stats.
If you want to limit stats to recent matches - you might consider using "Owned Custom Entities" for each match result. You can set a TTL for the objects so they don't stick around too long - maybe 90 days?
And then just retrieve the last 20 match results (if they exist) to sum up the totals and produce the stats.
I hope that helps!
Paul.
Hi @tlim ,
What sort of match history?
What sort of game are we talking about? Which multiplayer APIs are you using?
Paul.
Hi @LEE-JONG-GUN ,
Thanks for the feedback.
This is admittedly a tricky one.
The best route I've seen to handle it is to use our shared (i.e. parent-child) accounts feature - which involves using a parent app for the player account - and a child app for the character accounts.
Note that it does involve two live apps - but we can put your parent app on a special plan with no live fee (you just pay for API calls) - and there won't be a ton of API call from that app - cause 99% of all calls will be against the child app.
There is more info here - https://docs.braincloudservers.com/learn/key-concepts/authentication/shared-accounts/
I hope that helps!
Paul.
Ah - perfect. Yeah - that sounds like a better option given the full requirements.
Glad you found it... and welcome to brainCloud!
Hi @devsleeper ,
I think I'd recommend you model "Location" as a Custom Entity collection. You can use the "entityId" as your shareable id... and include custom attributes in the "data" section of the object - like "data.includeInMatchmaking", etc...
It would probably best be an "Owned" entity - so if the user account that owns it is deleted - it is deleted as well.
I hope that helps!
Paul.
Update - we've confirmed with the server team that we believe we are all set.
We'll perform some tests when the Sandbox servers cut over the week of Jan 20th to confirm.
Paul.
Hi @Darren-Wood,
Thanks for reaching out. I'll pass this through to the devs to investigate.
Here's the developer bulletin for those following along: https://developer.apple.com/news/?id=09za8wzy
My first thought is whether you need to regenerate the SSL certs that are used for generating the necessary push notification tokens. But that last line seems to confirm that that is NOT necessary:
"At this time, you don’t need to update the APNs SSL provider certificates issued to you by Apple."
This part does imply a potential server-side change:
To continue using APNs without interruption, you’ll need to update your application’s Trust Store to include the new server certificate: SHA-2 Root : USERTrust RSA Certification Authority certificate.
The quick reading I've done says it's likely that our servers already support that trust store. It's been available since 2015 - and we update our base images regularly.
And to confirm - everything I've read says that you shouldn't need to change anything in your app's client-side.
That said - we'll be sure to test it out.
Thanks for bringing this up! Our team will be looking into this as soon as they return from holidays - which is the week of January 6th.
Cheers!
Paul.
Resources:
Hi @kinco-h - I assume (hope) you got the info you needed from our support folks?
Hint - you access chat support by clicking on the "Ask Support" button in the top right-hand corner of the Design Portal...
Hi @wjurica ,
I do appreciate the perspective (for sure).
That said - 99% of entities are custom JSON - and most of our API objects have extensible JSON components. And of course - there are competing JSON libraries and approaches that devs use. Plus the complications of the capabilities of the different client+library platforms (Unity/C# vs. Unreal/C++ vs. JavaScript vs. Java, etc).
So - we've tried to have our libs take a light approach and focus on the networking + error handling + security
Your feedback is heard though! brainCloud is an ever-evolving platform. Never say never!
Paul.
