I have my leaderboard setup and everything is pretty much done. I'm just trying to figure out what to enter in the Score Attribute section of the actual behavior. Do I just select the high score table

Use Display Text to display the callback attribute and the contents of PurchaseTable cell 1,5. If that basic project works it's worth looking at your current code. If it doesn't (and the test project

splash screen has load attribute for if game has been purchased...

if touch is pressed, and if player number is 1, key input to change attribute (player 1 name) and so on for other player numbers

The callback attribute should just be any attribute you make that you use to store the response from the server. If it's -1 it can't connect and IAPs won't be able to be processed. If you get back -1

I'm also wondering what is supposed to be in the callback attribute? In the cookbook it says "self.Callback" but when I typed that in I noticed it doesn't save and just clears blank.

What will happen if I wont reset the "game.adreward.value" attribute to 0 after the ad as been delivered?

@bob loblaw Yes, we've seen that error too. Working on a fix, but for now you wouldn't see anything in preview anyway. If you're running it automatically I'd put in a rule based on a attribute for now

* Create 1 attribute in the game or scene. Let us call it "selected".

Change Attribute game.Numberofitems to (game.Numberofitems)+1

Change Attribute game.Numberofitems to (game.Numberofitems)+1

the bottom coordinate of the scene is 0. the top is 3000 (i think is what i set the scene size as). the camera height is 768. so those constrain behaviours stop the camera from reaching the full top a

May I ask you a one more question? You said I need to constrain min/max value of how it can move, but I’m not really sure how to do it because I literally don’t know anything about coding. Do I need t

in that case you probably need to constrain the min/max values of how far it can move, but use a camera that moves, not the image.

the example in this screen shot below is using the change attribute behaviour (renamed for my project) - using unlock is also the way you access attributes/values of other actors within a scene for ot

Sooo I did a test and my results shows a slight difference in favor of normal attribute expression in frame rate and against in total memory:

You have to have lowercase change attribute to false and the same goes to true, if you have it in capital it seems to not do anything and crash.

I have an actor with massive Numeric expression that compare against "0" so I can easily use Attribute expression with the max speed Attribute as the "0" against th

have a look in the pinned gdpr thread. if you’re using targeted ads, probably save the consent attribute so the user doesn’t always get asked if the same question.

And here the Android Free Lite Version: