You might be better off sticking to GameSalad terms to avoid confusion, I take it a variable is an attribute and you are using 'initialize' to mean change a value with the change attribute behaviour,

the problem is that it is only "pressed" when the touch is down so the sound must be checked 'run to completion'.....it's better to use an attribute system and then have a rules acto

@Armelline in the video Tshirt booth made this game.attribute integer called old score. I don't want the score to interplate when it's less than old score. I want it to interplate every time the score

That would work for one actor, but if you have more than one projectile on screen at once you would need to create two attributes for each, like you say it's not very efficient.

I did find a workaround just now although I don't think it's very efficient. I tried a universal attribute of X and Y, constrained it to the projectiles' position, then created a new actor with the ch

when attribute game.gameOver is false play music.

when attribute game.gameOver is false play music.

I don't understand what you are trying but if you upload a screenshot i can help. The best way for this is generally just one attribute and then set the image to the attribute..".png&quot

I'm using change attribute to change the image, and have tried both change attribute and constrain attribute to control the linear velocity.

I'll give it a go if you want . . . . How big are the images ? Also how are you able to tell whether the images have changed when they are out of sight (or doesn't that matter), and what are you using

@Braydon_SFX‌ I have made an attribute for each level.

In my purchase app button it changes the attribute to unlock game when purchased.

I'm going to guess (and it's only a guess) they used the change attribute behaviour ?

(Quote)

Well I was ad hoc testing before the GS update and it would auto rotate. After update it would not. I thought that was a game attribute anyways...so "global" across game. All set

Hi, I was trying to update the Angular Velocity with a Change Attribute behavior (this is on Windows). The behavior went like this:

when attribute self.motion.linear velocity x is > 400

I found the issue here. I needed to put the variable updates (both constrain and change attribute behaviors) within a timer within the Key event for them to continue happening while the key is down. O

Select the Wrap Y now you've found the attribute. Then simply look at the demo I put together and learn and copy the rules ive put in them. I never made you a template to tell you how to do it straigh

then save the attributes when they have been unlocked, and then load the attribute when the game loads.