Not using Pro, don't see that option for my "Rotate" attribute. Currently set for "Counter-clockwise" at a speed of 200.

@gyroscope Yeah I finally got it working. The problem occurred due to Gamesalad not waiting for the loops to finish before changing the attribute.

@gyroscope that's a bit different from what he's trying to do. He wants the first loop to run with a certain attribute set to 1 and the second loop to run with that same attribute set to 2.

There should be a "run to completion" checkbox for the sound attribute.

(Quote)

@tatiang @zweg25 Sorry for the poor explanation. Variable = 1 really mean change attribute variable to 1. I thought that the code ran down in order so I wouldn't have to specify that it should start a

.....Change attribute game.score to game.score + 1

Thanks a lot.

Does this mean "When attribute=1" or does it mean "Change Attribute to 1" ? And how are you making sure that the second part of that rule only starts after the fir

Have you tried it? Keep in mind that Every timers cannot be used with random values or attribute values that change. The timer will calculate the initial value and then keep that value. Instead, yo

* Create an attribute (game.myText)

looking for a way just to use the display text attribute.

but I I figured another way to do it, I just added a couple things. Instead of a timer, I added a rule. (This is on the gameover screen) as well as a save attribute.

still at random points in the y axis. I've tried constraining the attribute of the off-screen spawner from self position y to self position y and even changing the attribute on the spawned actor itse

(Quote)

I am still trying to understand the order it decides to follow. If I have 1 actor replicated 4 times one after the other with the same rule to constrain game.EnemyX to self.PositionX, how does the gam

A problem comes up when copy and pasting behaviors from project A.1 to project A.2. Even though I recreate all the actors, attributes scenes, etc, an error message comes up saying: "warning:

100 points...(for 1 sec, every .01 sec, change attribute "score" to "score+1"

Perhaps its because rules set it to constrain enemy2 and then immediately after that its constraining enemy1. Since enemy1 was the last to be constrained, its going to retain that one.

Sorry if I am confusing things. I don't have an issue getting it to work. I am just wondering why there is not a conflict when another enemy with the same rules comes into the zone trying to constrain