Change Attribute: game.random to random (1,3) <- tshirt said if there are 10 it should be (1,10) so if I add 3 more should I put it at (1,6) already at the start?

in each scene. Or… You can go into the scene attribute and click camera and then origin and set the origin you want right there.

high score the game score is saved as an attribute "highscore". I am noticing that when my score hits the high score everything starts to lag or act jerky every 0.5 seconds as the s

This gives me an idea, keep the bomb off screen, and constrain it to the X position of the player (or touch; try both), then when touch is pressed to interpolate the Y position

Couldn't you constrain the position of the bomb off-screen, to the position of the player? Then when you touch the button, it drops the bomb...

Couldn't you constrain the position of the bomb off-screen, to the position of the player? Then when you touch the button, it drops the bomb...

You could try to constrain its rotation to "0" but i'm not sure if its gonna work cos i haven't tried it (Image)

Create an attribute - (Boolean) Collided

After that, I fixed up some minor bugs / glitches. One of the annoying things about making a physics game in gamesalad is that if you have sound effects for collisions, they will all fire at the start

Constrain the characters X and Y position to two attributes. Then constrain the background to the middle of the scene minus the x or y position of the character.

If you got any rules involved (boolean or integer etc.) try creating a text actor showing that specific attribute see if the rules change for any reason at the time the black hole happens when it shou

And use constrain,as that will constantly update that attribute to be the same as the position at all times, change attribute will only do it once

i create two game attributes,platerx and playery, which one should i use, real attribute or integer? and should i use

Where you have the change attribute game.score to game.score-50 just change it to change attribute game.score to max(0,game.score-50). Hopefully that should do the trick.

Each and every attribute you make has to be reset if the situation calls for it. It's really not that bad considering the alternative…Which is actual coding.

@RH: Thanks for your reply. I have looked over the project for attribute errors, but the weird thing is I can even tap a button that worked fine prior to this even though that button has no relations

Definitely sounds like a user error rather than a bug. I know you've probably been over it several times but it's most likely to have been caused by a mis-used/ missing attribute somewhere so I'd have

For the score, in the rule that destroy's the enemy or takes health off the enemy, change attribute game.score to game.score+(the amount of score you want)

1) constrain a invisible actor with static size 170x150 to its position

I've had trouble with that too. I think you have to manually reset each attribute.