• Discussion - Promotions

    Unsolved General
    10
    0 Votes
    10 Posts
    208 Views

    @JasonL
    Looking back, I realized I forgot to mention a couple of things—sorry about that. I'll list them here:

    Is there a way to determine how many purchases a user has made of products affected by a given promotion? This is especially relevant for automated promotions, which have a "max purchases" value but no "purchases left" value in their data structure.

    For automated promotions again, is there a way to check how much time is left before a promotion is disabled? A Unix timestamp indicating when the promotion became active would be useful for this purpose.

    Both values would be helpful for displaying accurate promotion data to the user across multiple sessions.

  • PostTournamentScoreUTC DateTime or ulong?

    Unsolved APIs
    4
    0 Votes
    4 Posts
    67 Views

    Okay - cool!

  • propark.cloud

    Unsolved General
    2
    0 Votes
    2 Posts
    61 Views

    สวัสดี ต้องขออภัย แต่เราให้บริการช่วยเหลือเป็นภาษาอังกฤษเท่านั้น

    [Hi. Apologies - but we only provide support in English.]

  • Post Score when a Tournament ends?

    Unsolved General
    2
    0 Votes
    2 Posts
    101 Views

    You can schedule a recurring daily cloud code script to run after the completion of your daily tournament. This script will use the GetGlobalLeaderboardPage method to retrieve the daily tournament winner's information and score, then post it to the monthly tournament using the PostTournamentScoreOnBehalfOf method.

  • Recurring scheduled tasks?

    Unsolved Cloud Code
    6
    0 Votes
    6 Posts
    190 Views

    We agree with that @antony - we'll get that request to the devs.

  • 0 Votes
    8 Posts
    235 Views

    Hi folks,

    FYI, here's one minor update regarding the Retention Analytics screen:

    We have changed it to show Classic retention by default.

    The reason for the change is that Rolling Retention naturally trends downward over the 30-day period of the report. That's simply due to mathematics. Rolling retention for a particular day measures whether the user returns that day - or any day thereafter. Thus - the days at the end of the calendar period have fewer days after them - and so the stat will naturally be lower.

    We don't want folks to mistakenly think their retention is trending down - so we're now defaulting to Classic Retention which is more deterministic over the 30 day period. For those who wish to view the Rolling Retention - it's just a mouse click away!

    Cheers!

    Paul.

  • Match history

    Unsolved General
    8
    0 Votes
    8 Posts
    290 Views

    thx, I will give it a try

  • 0 Votes
    2 Posts
    101 Views

    Thank you for sharing this information. It does not have an impact on our server-side validation.

  • 0 Votes
    3 Posts
    2k Views

    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.

  • Global Entities retrieval issues and questions

    Unsolved APIs
    5
    0 Votes
    5 Posts
    245 Views

    @wjurica Assuming you're using c#, consider Newtonsoft for the deserialization & mapping process. It's two lines of code to map your data to a class.

    https://www.newtonsoft.com/json

  • bridge.getCustomEntityServiceProxy()

    Unsolved Cloud Code
    5
    0 Votes
    5 Posts
    306 Views

    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...

    2024-12-04_09-07-57.png

  • Localization Issue

    Unsolved General
    6
    0 Votes
    6 Posts
    254 Views

    Thank you so much!

  • 0 Votes
    2 Posts
    134 Views

    You can achieve it by writing a cloud code script that retrieves the data of each individual user's user entities and stores it in a custom entity collection. After that, call the method RunBatchUserScript() to execute this process for every user within the app. Then, the resulting collection can be downloaded for analytical purposes.

  • 0 Votes
    8 Posts
    352 Views

    For clarity, Firebase Cloud Messaging recommends creating a topic using Pub/Sub, though this approach is optional.

  • Dedicated server getting all player's username

    Unsolved General
    5
    0 Votes
    5 Posts
    323 Views

    Oh, server can use client API

  • latest braincloud xcode build error

    Unsolved General
    4
    0 Votes
    4 Posts
    205 Views

    Okay, I built it using the commented out part above.

  • 0 Votes
    2 Posts
    178 Views

    Hi there- thanks for bringing this to our attention! A newer version of the Unity Package containing a fix for this has been uploaded. Available here: https://github.com/getbraincloud/braincloud-csharp/releases/tag/5.4.1

  • Don't reward quests + milestones automatically

    Unsolved General
    3
    0 Votes
    3 Posts
    185 Views

    one workaround im thinking of doing is having a "fake" user stat. one that tracks the actually XP and another that's "unlocked XP". then just increase the unlocked XP whenever someone "claims" the milestone

  • How to implement "loot boxes"

    Unsolved General
    2
    0 Votes
    2 Posts
    171 Views

    brainCloud doesn't directly support loot boxes currently... Though of course the Item Catalog and User Items services give you the building blocks to construct your own system in cloud code.

    To implement such a system, you would:

    use Global Entities or Unowned Custom Entities to represent the collection of loot box templates construct your JSON with the rules (percentages, etc.) for constructing the loot box then write a cloud code script that when run - performs the work to award the user the relevant items

    Note - there are future plans to add such a feature to brainCloud - but it isn't scheduled yet. I'll add your +1 !

    Paul.

  • 1 Votes
    9 Posts
    613 Views

    @Brad-Hester That bug has been fixes (and patched). Thanks for reporting it!