change attribute is a one time thing. Constraining an attribute is constantly keeping an attribute to something or another attribute (Image)

I have a timer that spawns enemies at intervals of the attribute "Spawn Timer" (every (Spawn Timer)) and I did a change attribute above it that lowers the attribute 0.1 every 2 secon

If attribute device.IOS is less then 4.1

when an actor comes to a halt it only registers collisions and then starts calculating all sorts of stuff. The actors also change in size depending on where they are on the y axis (3d simulation). Wh

yes lets say your attribute = pie, make another attribute called original pie original. Change attribute original pie to pie original. When pie doesn't equal pie original you know you have a change (I

yes lets say your attribute = pie, make another attribute called original pie original. Change attribute original pie to pie original. When pie doesn't equal pie original you know you have a change (I

But i cannot have it done when i use the change attribute (+1), primarily because it would start to get far to complicated to follow. (development wise). So any suggestions?

Rule- If attribute combometer > 0

hey glad you figured it out, sorry about before. Just so you know for future references: in a rule "attribute" will never = "same attriubte" + 1

use change attribute instead of move and change the x and y to exactly what u want. Move doesn exactly that, it moves it thats why its slidding

So I used a rule that when stop is pressed, attribute game.BallMove is false. So then, under the ball I said, when game.BallMove is false, "MOVE", and entered the coordinates of the

keep the walls unmovable and set the touch controlled actor to movable. GS does not detect collisions between two unmovable actors.

I would use one actor with seven different images. Image one has the first section dark, image two has the second dark, etc. To constrain 7 actors together is going to kill your performance.

I would use one actor with seven different images. Image one has the first section dark, image two has the second dark, etc. To constrain 7 actors together is going to kill your performance.

The problem is that I don't want part # 1 to always be part # 1 and part #2 to be part #2 and so on. So I created an attribute that say when this happens change submarine to random(1,7). If it is 1 pa

Anyone else think gamesalad needs a global popupbox for easy access to any attribute (global or local)? It could look like the interface builder one

for your question for each scene youll need a attribute to represent its score, as well as a rule in each scene when its corresponding attribute is > then whatver change scenes

2. Yes, it is. When you open your actor, or instance, there is a text attribute "Image" on the left, there will be something like that: xxx.png. Just click this, and then click Delet

Timers don't work with random yet unfortunately. there could be another way to set an attribute that picks a random number and based on that number you can set a bunch of different delay timers for yo

Timers don't work with random yet unfortunately. there could be another way to set an attribute that picks a random number and based on that number you can set a bunch of different delay timers for yo