When attribute self.color.alpha = 0

Interpolate attribute self.color.alpha to 1

But as I explained above, when touch is pressed and you interpolate alpha to 0, it triggers the first rule:

You will need to make 2 real or integer attributes (game) and constrain them to the hero's X & Y position.

(Quote)

I usually constrain another actor to the main one, in the layer below and put the particles in there.

But if I don't change scenes, what occurs is an endless loop of the actor fading in and fading out. This makes sense because every time you click on the actor and the actor's attribute self.color.alph

Now here's the thing. I would like to create a custom pause button but GameSalad would not know to use that when a notification interrupts the gameplay, right? So that leaves me with one other option.

I did try the change attribute, and it didn't turn my actor at an angle while it turns.

Yes, let's say your actor is facing up (90°) and you want it to turn right (0°). You would do Change Attribute self.rotation to self.rotation-90.

change attribute self.rotation?

If you want an immediate rotation change maybe try a Change Attribute Behavior and change the actors rotation to whatever you want it to be.

game att . does that affect my save and load attribute for my highscore system

If i have a play again button and also a menu button at my game over screen.. what do attritube do i use on those so that my save and load attribute still works?

@justinodunn‌ I'd like to make a suggestion - Decide on which part of your programming you want to report a problem on and stick to it in the one thread... I know your different explanations of probl…

Yes I put those and it still didn't work. THe scene lock attribute is meant to trigger this other scene lock attribute. That other scene lock attribute will then change the opacity of the "lo

Rule set to Any: When highscore x <250 or total score < 12000Change Attribute YourActor.Alpha to 1Change Attribute scene lock to falseOtherwiseChange Attribute YourActor.Alpha to 0Change

When "highscore x < 250" or when "total score < 12000", change attribute self blue/red/ green to 0. change attribute "scene lock" to

So to summarise what the other guys said, your Rules should look like this (assuming "x" is just a substitute to show an actual number, not an attribute holding a number):

We're you using a constrain? If so that won't work, you need to be using a change attribute.