General

Discuss all the things!

146 Topics 521 Posts
  • This topic is deleted!

    Unsolved
    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • AWS Gamelift integration guide

    Unsolved
    5
    0 Votes
    5 Posts
    93 Views

    You can find the Knowledge Base link on our documentation site, which is linked to https://getbraincloud.com/.9b4015ab-4420-4d80-9368-5accf73b92c8-image.png

  • 0 Votes
    3 Posts
    42 Views

    I see! So if the schedule hasn't started yet, changing the reset cycle resets everything, including the rewards. Thanks for letting me know!

  • 0 Votes
    3 Posts
    39 Views

    There are multiple leaderboards in the game separated by region, but aside from the region itself, they all use the same settings.

    When creating them initially, cloning works fine. However, after they have been created, if I need to adjust various options, I have to edit each leaderboard one by one.

    The main problem is that every time I save a change, the “Updated successfully” popup appears and covers the edit button, which makes consecutive edits across multiple leaderboards very inconvenient.

    It would be much more efficient if there were a way to edit multiple leaderboards with identical settings at the same time. At the very least, moving the success popup to a location where it does not block the button would greatly improve usability.

  • 0 Votes
    10 Posts
    121 Views

    Thank you! 🙂

  • 0 Votes
    14 Posts
    182 Views

    Symptom
    After updating from 5.9.2 to 5.9.3, iOS/iPadOS experiences gradual performance degradation during extended play sessions, eventually leading to app termination
    This issue did not occur on 5.9.2
    Suspected Code
    In BrainCloudComms.cs - HandleResponseBundle, the following line was added in 5.9.3:

    jsonData = JsonWriter.Serialize(JsonReader.Deserialize(jsonData));
    Concerns
    This performs a full deserialize → reserialize on every API response
    Immediately after, DeserializeJsonBundle parses the same data again — effectively parsing every response twice
    Each response generates a large number of temporary objects (Dictionary, List, boxed values, strings) that are immediately discarded
    On iOS with IL2CPP (Boehm GC), could this repeated allocation/deallocation pattern cause managed heap growth over time?
    Question
    Could this code potentially contribute to memory-related issues on iOS during extended play sessions?