for the first two matching cards have match =0maybe when you touch the first one when touch is pressed change attribute match +1 when second one is pressed change attribute match + 1 . when match = 2

Yes I been around that idea but after that my brain just crash. I was thinking like making an attribute called match and every picture has this attribute with a number, but how to tell the game when

For the flipping back and forth you could just animate it. And im guessing each picture would have to have its own attribute to check when touched and the matching ones would have the same number so w

change self attribute Speed(int) to self speed(int) +100

I tried that last night, but it didn't work. Maybe I need to set the timer longer. Since that rule didn't work, i figured it was reading collisions after the timer went off.

Make sure your rule has an otherwise change attribute to false or if you want it to do something special when it leaves the actor and changes to false create rule for when it changes back to false.

I have two actors and a boolean attribute that changes to true when one actor overlapes another but how do I detect that an actor is no more overlapping another? I've tried using boolean and integer a

ChangeAttribute game.numberPick ...To: random(1,100)

--Change Attribute: self.Image To: "score_"..floor(( game.currentScore % self.divisor )/( self.divisor /10))..".png"

Hi MotherHoose. Thanks for saying that you use index attribute because I have never used them, I don't even know what you can do with them... Since you use them a lot, can you explain them to me, plea

Constraining something to the mouse takes precedence and overrides all collisions.

I see array being just another variable type that you create, and when you select an array variable in Change Attribute or Constrain Attribute behaviors, an 'index' box appears (with the same options

idk, let's say you want 1,000 different values for 1 array.... then, when you want different values pulled from that array, you don't have to go and create an attribute for every single numerical attr

instead of a new attribute like boolean, integer, real... Just add a '+' button for an array of that data type which can be set to any length

instead of a new attribute like boolean, integer, real... Just add a '+' button for an array of that data type which can be set to any length?

In the first screenshot, the mission brief is activated. The computer console moves into the screen with an interpolate. That's simply activated with a rule and an attribute...

Constraining something to the mouse takes precedence and overrides all collisions.

if you constrain x to origin.x +240 and y to origin.y+160 for landscape

I need to know if by any chance it a way to get the coordinates of the center of the camera while its moving to constrain those values to an attribute... any help?

Then drag in a change attribute behavior from the list of behaviors on the left