I'm wondering what Attribute I'd use to spawn my blocks based on where I touch on the screen? Right now I just have them spawning from a block "container" that when touched spawns so

If your Score variable is a global Game attribute like Eastbound indicated, just use the same rule check for collision in the shark in the fish as well.

Make a global attribute called score. When they collide set score = score + 1

how about trying interpolate instead of a timer. To vary a game attribute, incase that works instead of a timer...

Every 8 seconds change attribute game.animation (random x,y)

um .. maybe use a global attribute called animation

@stormy - I'm not on a Mac to look at Bark's solution but from the sound of your solution's issue regarding the second touch and the actor's rotation snapping back to some position upon second touch r

You can save games, just use the save attirbute and load attribute

Double-click on an actor on the stage and that brings you to the instance editor. You will see that most of the attributes are grayed out until you "unlock" the instance. Don't unloc

Create an attribute called 'Score'.

I think you need to constrain X, Y of the object to this

2. For the moment vision range is limited to increase game difficulty. I've designed levels in a way that constrain player to memorize a little level's structure ( levels are not very big ). But yours

Im putting a load attribute rule for my high scores button but the high scores will still not show up when the app is exited and re entered. The saving keys match but the scores are reset to 0.

My Game attribute is GameIsPause - unchecked box - boolean.

Do you have a load attribute anywhere in your game? Without the load attribute, the game wont load saved data.

be easily remedied by creating a boolean Game Attribute called "select-lock". When any object was selected, select-lock would be set to "true". When the object bec

Make sure you create an attribute for the save, and name it "highscore"

do I need to change the accelerometer values or something? is there a why to constrain the portrait orientations to lock them or to turn them off ?

constrain: self.position x to floor(touch1.position.x/2)+floor(touch2.position.x/2)

constrain: self.position x to floor(touch1.position.x/2)+floor(touch2.position.x/2)