pretty straight forward question. not sure how to be more clear. need the cam to constrain to actor in the lower 3rd of the screen. maybe visual ref may help. (Image)

Yes constrain instead of change , and don't forget to set the bounciness to a low value,try and tell me if it works

So if right arrow is pressed, constrain instead of change? Would constrain go through the edge? I will try it out sometime today.

Use constrain linear velocity instead , then try setting the bounciness to a low value, try 0.1 or 0.09 , play with the value.

Good to hear the progress as always. I'm super stoked you got custom collisions (and a preview!) and all the behaviours ported. Can't wait for full feature parity.

Hello I was wondering if there was any way you can make an attribute happen every 10 times. I have a score and when it hits multiples of 10 then I want to display the score in big numbers.

Custom Collisions

of questions from rows 31-60, you would Change Attribute game.nextQuestionText to tableCellValue(tableName, random(31,60),1). To limit it to 20 questions, you might change the random range to somethi

Yes. Integers are whole numbers. So if you want decimals, you need to use a real attribute.

* real attribute:"faster"="2"

What type of attribute is game.score and game.high_score?

* On your shop scene, you need to have a -10 coins change attribute, when the purchase is completed.

Does the coin counter attribute exist in the actor or as a game level attribute?

I'm stuck on setting up coin counter attribute.

(Quote)

Thanks Armelline! right, I totally forgot about the linking attribute.

Your IAP button should be changing a game level attribute or table cell that tells the game if ads are disabled or not. All places that would display an ad will then check that attribute. No need for

all in one document. If I find a particular attribute is not behaving as I expect I can then search the document for reference to the attribute and work back through the logic in my algorithms to hel

At the moment I'm using a display text rule to watch the value of an attribute, which is increasing is twice as quick as it should.

And there is no dialog when deleting attribute in WIN verison