It's all very doable but I'm not sure what you need help with. You asked about "how to add the actors to a separate scene." You can definitely spawn an actor in the same scene but

Correct, though you don't need a rule at all. You'll just need the privateDataConsentForAds attribute that's set to 1 hardcoded in your game for ads to display normally.

(Alternatively, you can create a game.attribute (real), and use this as the speed value. This way you can change all behaviours speed value at once.)

Nevermind, fixed it. Used change attribute: self.motion.linear velocity.x for x movement instead of change velocity.

attribute: self.gravity is true

attribute: self.gravity is true

3) If you're using ads, this update adds support for the previously mentioned privateDataConsentForAds attribute, which can you use to indicate that your users have given permission to the ad networks

For the most ad providers, yes. The exception being that AdMob ads will show if the attribute is set to 0, they just won't be targeted ads.

So just to be completely clear on this - the new attribute needs to be named 'privateDataConsentForAds' exactly. And it will be coded within the game engine to look for this attribute and then intial

textSubStr() is a function that returns a portion of a string (aka text attribute) from the character position of the first value to the character position of the second value. So textSubStr(turkey,4

You might want to do this without a constrain behavior. Not sure exactly how your game is set up since you didn't provide a lot of details but you can probably just have the goal (or whatever DualObj

What is gamePosY? Did you mean to write game.goalPosY? Also, any time you're using position values you're going to want a Real attribute rather than something else (definitely not a Boolean since th

Constrain the game.goalPosY to DualObj.PositionY

TL:DR When the update is out, everyone will need to re-publish their apps to be compliant. Those who are showing ads will need to add a new game attribute to their game and get consent from their play

I wasn't very clear but the idea of a text attribute is a bit more advanced perhaps conceptually as well as more efficient code-wise:

when hitting wall, maybe animate when self attribute is greater than zero... sometimes you wont get a response when its hard to understand the problem. You did put lots of details in post but still

I like your idea of using a text attribute in the table. I might try to dynamically add each scene name to a table to isolate the coins on that scene.

It's really about keeping track of the number of coins either as a static value (e.g. scene 2 will always have 13 coins) or dynamically (e.g. change attribute game.spawnCount to game.spawnCount+1, spa

Then you'd need a table - or I'd actually use a text attribute but let's not get sidetracked -- like this:

I've added the reset of the game.NextCoin attribute.....