Is that what you meant? Because unfortunately it's still doing the same thing. 5 or 6 of the clues activate and then it just stops. Should my game.RandomClues attribute be an index one like it is or a

(Quote)

Your rule is deleting a row and then choosing the row to use. Switch those two behaviors so that the Change Attribute is first and the Add/Remove Row is second.

My global attribute that I'm using is an index attribute. So after making this effort I tried it out and they still repeat themselves and only 5 or 6 out of the nine clues even show up. I would be ver

hello. I have some attributes in my game. but when the player closes out of the game and reloads it sometime later, how do I keep that attribute, save it

Make a timer that...every 1s change attribute game.timer to game.timer+1

(Quote)

(Quote)

Constrain X position to: 22 *sin( self.Time *99) *sin( self.Time *191)+512

To check for collisions, you would use a Collides or Overlaps With condition. The actors do not need to know the coordinates of other actors to check this.

@abuabed84 What are you changing the new position to in your change attribute?

Example: I double click an actor (10 seconds) loads the attributes, I change 1 attribute (10 seconds) changes the

Make a real self attribute in the platform actor of either your platforms x or y location and have a rule that changes the real attribute to the location of your platform, so if you want to lock its x

* In the layer if the platform is above the player the constrain does not update before the player and they get out of sync. (This was mentioned in the tutorial, thanks Jamie (Image)

Ok, I may have solved this myself. I have put the constrain behaviour in a rule that is only triggered when colliding with the player. It appears to work at the moment, however I tried this yesterda

Change Attribute game.random to random(0,2)

I made a game integer attribute called GameplayBG and set it to 0.

You'll need a separate Key for each unlock. If you have more than about three values to store, I'd highly recommend using tables instead of Load/Save Attribute behaviors.

correction, 1st picture is the load attribute which is at the begining the "click to play" scene. 2nd one is the lock and 3rd one is the actor collides w/ to unlock next level

the lock on the level. the 3rd one is the load attribute