You could create a list of vehicles and an integer attribute called Selection. Give each vehicle a number. When one is tapped change game.selection to that number.

Create an boolean attribute called flying. Whenever the plane starts flying change that to true.

He expanded the camera to expose the whole scene. Expanding the camera can cause issues with an actor touch area especially when you're constraining an actor to touch. To correct this you'll need to c

If you base your timer on a built-in time attribute such as game.Time, there is no way to reset it. If you need to reset the timer, you'll need to instead use a custom timer. One way to do this is t

So far as resetting the score, you need to have a game attribute which is an integer. Set it to 0 and in your game rule where you die, do a change attribute of game.Score to 0

You've a change attribute set Alpha to zero behaviour in the actor

Basically, you can create an integer attribute. If the card is ace, k, j, q or 10, change that integer value to -1. If 2,3,4,5,6 change it to 1. If 7, 8, 9, change it to 0.

Hi @justinodunn One way: make an integer attribute, lets call it NumColl, leave it at 0 to start.

Maybe you could make it a little clearer, try stick to standard terms, for instance use 'attribute' instead of 'integer' - and lines like this: ". . . added a -1 +1 to each of the numbers sel

that would be one way, however, i would like to save ram wherever i can. can i not just have the actor go to the first row, then have a +1 attribute to go to remaining rows in order?

If you have lots of actors you need to position on a whole pixel value, you can make a change attribute behaviour like this . . .

Wherever your rule is that starts the game over, add Change Attribute game.score to 0.

@deepblueapps good idea, I have just approached it slightly differently but kind of the same effect, seems to have worked - created a boolean game attribute called triggercam and set a rule that when

booth that shows how to use control camera attribute. Using my phone otherwise I would post a link

Could you interpolate the camera position to the actor at the start then constrain it?

You have to constrain actor 1's x and y positions to actor 2's x and y positions. That way any change in actor 2's location will affect actor 1.

There are no custom collisions at the moment @daaddd. You will have to find another way.

You could make a smaller actor turned 45 degrees and constrain it to the x and y position and use the smaller actor for collision.

I'm triggering it via a Constrain Attribute: self.Integer-value tied to a Table value.

Instead of using self.Visible, use the self.Color.Alpha attribute. Simply change that to 0 or 1. The value of 0 will make the actor invisible, while the value of 1 will make it visible.