Yes, I actually started it that way, or at least was thinking of making it a 2plwyer game. I could be a bit concerned for constrain, if it will be precise enough. I'm planing to get it out one of the

Only time I get an issue like that is when I use a change/constrain attribute with self.image rule and I don't have the naming convention right in my actor's rule.

I'm probably one of the few Gamesalad GodSalad users that develops on a PC instead of a Mac. When I started 2 years ago the Windows creator was at version 0.10.4. The program was very buggy and crashe

@Are Skarstein Kolberg most likely you are setting your text behaviour before you have loaded you highscore attribute.

Control the image using a integer self attribute.

Change Attribute game.HighScore to tableCellValue(HighScoreTable,1,1)

function, adding 1 to score for each sec (change attribute-->"game.score+1"). When the game ends the scene shifts to a "game over screen" displaying the sco

function, adding 1 to score for each sec (change attribute-->"game.score+1"). When the game ends the scene shifts to a "game over screen" displaying the sco

and the constrain att: game.myTimer -to- game.myTimer+10

I made a real game attribute myTimer set to 60 and added the rules to main character I can't seem to figure out why its not working

You need to create a new self interger attribute, let's call it randomtext. Then, set that integer to a random number, matching the number of responses:

Hmmm yeah I do have can sleep checked and better collisions unchecked! Will try that (Image)

Do you have can sleep unchecked and better collisions checked?

Here's another way, make a real attribute 'A', set it to to 60:

As the title suggests I'm finding that if I have a custom collision actor that rotates, the collision data will become out of sync with the actor after a short while!

Add camera origin x and camera origin y to your constrain x and y.

constrain: game.myTimer to 60-(game.Time-game.startTime)

I want to move touch an object and drag it around the screen. This is fairly easy: just constrain x and y to touch x and y.

Out of interest, why is having the width increase directly in the constrain smoother than constraining to an attribute that is modified?

I have an self.offset attribute