bitHeads group

Paul Winterhalder

Hi - so we highly recommend that apps using brainCloud utilize the client APIs for interactions from game clients. That API is purpose-built to represent a player -- the entire api is implemented from the perspective of a player of the player - and the built-in security model supports and enforces this.

Mimicking that via S2S is not recommended. It's inefficient and error prone.

Feel free to reach out to us via the support widget if you'd like to have a deeper conversation regarding what you're doing and why.

Thanks,

Paul.

Paul Winterhalder

Can you copy the errors here or send us a support chat message with them?

Paul Winterhalder

Awesome - great to hear!

JasonL

You're correct: there's currently no API to query users by owned item (defId). All UserItems read operations are scoped to a single user. We've noted this as a feature request. In the meantime, rather than adding storage logic to every purchase flow, you can attach a Post API Hook to the item award/purchase/drop operations. The hook script maintains an index for you (e.g. flags in summary friend data searchable via FindUsersByUserSummary).

JasonL

The production app most likely has "Show Game Design Features" switched off. It's a per-app setting under Advanced Settings

JasonL

Could you share what you're using last-login time for (e.g. dormant-user cleanup, segments, promotions)? Last login drives several systems, including dormant-user identification and login analytics, so setting it without a real login would affect more than the display. If we know the goal, we can recommend (or consider) a more targeted option, such as tracking a separate activity timestamp or excluding those users from dormancy.

Paul Winterhalder

The fix for this has been deployed... (a couple weeks ago actually - apologies for the lagging notice!)

JasonL

We also strongly suggest using the ProductManagement service through a Cloud Code script to create and manage products programmatically, rather than entering them manually in the Portal. This can help automate catalog setup and make it easier to maintain product definitions in your own workflow. Please see the documentation here: https://docs.braincloudservers.com/api/capi/productmanagement/

JasonL

Thanks for the suggestion. I’ll forward this feature request to our team for review. In the meantime, depending on your use case, you may be able to reduce the number of store product IDs you need to manage by using CachePurchasePayloadContext(), introduced in brainCloud 5.8: https://updates.braincloudservers.com/?query=CachePurchasePayloadContext. It lets you cache additional purchase context before the transaction so brainCloud can combine it with the receipt during verification, potentially allowing product IDs to be reused across different items, offers, or price points.

Paul Winterhalder

Hmm - I'll get the team to take a look at it.

bitHeads

Posts

Member List