Create an integer attribute and call it something like Random Blink Animation.

I had a similar problem too. I made a game.attribute that is an ANGLE. Then when I do my 'shooting' rule, I have it change attribute game.PlayerRotation to self.rotation and then spawn actor from -gam

Instead of having all your numbers constraining all the time, figure out how to change some in a change attribute instead based on rules. So for example your 1 million only changes to 2 million when t

create an invisible actor that is a good size (alpha set to 0). Then have that as what is controlled by touching and the only rules in the firemen actor is to constrain it's position to the invisible

Thanks GSLover. However, that demo is exactly how TSB made his video. The issue is that I have 8 actors all with a constrain attribute on them and my performance sucks (might not all be due to the sco

events instead of having extra atributes and constrain and a timer

change attribute self position y to 0, and change attribute self position x to random(0,320)

You could just add a random x & y (put a limit so it wont go outside the scene)to your main actors constrain position sO it wont miss a spawn time.

You could have a constain attribute on the ball's X and Y position (let me know if you don't know how to do this). Then create a rule in the enemy spawner; Every 5 seconds AND magnitude > 100 f

You could have a constain attribute on the ball's X and Y position (let me know if you don't know how to do this). Then create a rule in the enemy spawner; Every 5 seconds AND magnitude > 100 f

So I have a scene which will end and change scene if a moveable actor tag collides or overlaps with a non-moveable actor. The moveable actors are fairly complex as when touched they are constrained to

I watched TSB's Custom Font Scoring video. I followed it perfectly. He suggested to me instead of using so many Constrain Attributes on my scoring actors (Players can score into the millions, so that'

if player1score = 0 change attribute TennisScore1 to 'love'

If after your change power up number to 0 rule, you have a change attribute and set self.motion.linearvelocity.y to 0, that should stop it from moving.

I might try setting the change scene attribute to if the actor's x co-ordinates are > etc.... instead of a collide and see if that works, off to bed as my brain has melted again... will try th

Just a previous scene behavior would be the easiest to setup. Why would not want that. If you set up rules to load each individual level based on an attribute you will literally have a button that you

Well I'm pretty new to GameSalad but I think you could have an attribute called lastlevel (for example) that would be updated with the level number each time they enter a new level. So if they start p

So I have a scene which will end and change scene if a moveable actor tag collides or overlaps with a non-moveable actor. The moveable actors are fairly complex as when touched they are constrained to

it should be like this. Have you 2 real attribute lastx and lasy

youll need 2 make 2 real attributes callthem playerx and playery and in the actor constrain playerx to self position x and constain player y to self position y