Okay - it looks like that script may be callable via cloud code script in S2S - but not via the S2S api directly... The devs are looking into it.
bitHeads
bitHeads employees
Posts
-
SYS_UPDATE_CAMPAIGN_JSON (Campaign S2S) returns "Unrecognized request" even though our app is already running 6.0.1 -
SYS_UPDATE_CAMPAIGN_JSON (Campaign S2S) returns "Unrecognized request" even though our app is already running 6.0.1Hi guys,
Can you still get this error? We can't repro it?
Paul.
-
Integration streamHi Noah, thanks for the follow-up. Yes, for virtual item purchases, the stream event is triggered immediately in the same request flow, right after the purchase is finalized and verified. So the trigger point is immediate.
That said, the event delivery to downstream systems such as Kafka, Segment, or the Mongo log is asynchronous and queued, so it should not be treated as a synchronous low-latency real-time event.
We’ll also review your feature request for a Stream HTTP Webhook and will keep you posted.
-
[Feature request] Support multiple Apple client IDs (aud values) for AuthenticateAppleAwesome. Thanks for confirming @lee-jong-gun !
-
Request to add unique indexes for Custom EntitiesActually that should work now @moondory77 . You just have to include "unique": true in the options.
-
Subject: Inquiry regarding selective CustomEntity migration via Builder APICool - glad you found it!
-
Confirming Campaign feature write API limitations and Trigger timing (v6.0)Hi @jongdae.won ,
brainCloud 6.0.1 has been deployed. The Campaign Analytics feature - as well as the APIs for updating the campaign and scenario JSON, are now live!
Paul.
-
How should Cloud Code read a Global Property flagged Secret?Hi @gyutaelee ,
Use the direct global property call from the bridge. It will return secret properties.
https://docs.braincloudservers.com/api/cc/bridge/getglobalproperty
i.e. bridge.getGlobalProperty(propname);
I hope that helps!
Paul.
-
Confirming Campaign feature write API limitations and Trigger timing (v6.0)Hi Jongdae,
Great questions!
Before I answer them, though - heads up that we have an update to LiveOps campaigns coming next week. It provides a great analytics screen for campaigns, so you can see how they are impacting player engagement, monetization, retention, etc.
That said, you are pointing out some additional caps that we'll want to address quickly:
-
The management APIs for campaigns are following in a future release - but we can see about getting some APIs that specifically target updating the custom JSON for campaigns and scenarios. I'm going to see if I can slip that into next week's release.
-
Right now campaign enrollment is only triggered upon login. We're planning to add an optional "trigger": true flag ot the getMyCampaigns() call, though - which would allow games to make that call periodically (i.e., after the player finishes a "match," perhaps), as makes sense on a per-game basis. Longer-term, we are considering adding an RTT channel that clients could listen to to be notified of when a new campaign launches...
-
Feature maturity - with the 6.0.1 update that we're releasing, the feature is mature enough to build upon. We'll continue to extend it, but we can do so without invalidating the foundation we have built.
-
Cross-environment campaign management - we'll be adding some features to allow easy importing / exporting of campaigns between environments. Plus the S2S management api will help too... All coming this fall!
I hope that helps,
Paul.
-
-
Integration streamHi @noah ,
brainCloud 6.0.1, which will be released next week, adds new data stream events for virtual item purchases.
We'll keep #2 and #3 in mind as we continue to evolve things going forward.
Thanks for pointing out MongoDB CDC - I wasn't familiar with that capability before. We'll take a harder look at it.
Cheers!
Paul.