Use magnutide. You dont want to constrain another actor to the first of if you dont have to.

Choose a random number from 1 to 3 using Change Attribute. Attribute maybe rdm#

Change attribute: game.RndCard to random(1,52)

if you use the magnitude attribute? or pazappa's suggestion also works

If attribute game.level < 5

New Game attribute, lets call it - Score.

Sorry for posting this so many times, however I havent been able to get an answer. I really need to get my actors of the same actor"type" to register individual collisions with anoth

When you press the actor, if the attribute is true, it sets it to false, then the other rule kicks in because it sees that the attribute is false and sets it to true.

When pressed / if musplay is true (music is playing) - pause music, set musplay to false, save musplay attribute

In the first image you have constrain self.height to two different things. That doesn't seem like a good idea.

Hi trp, no way to do that, i.e no database type elements at all in GS. So it's putting your music lengths into the attribute values one by one, sorry.

Hi AppsforCameron; that's quite straightforward, you need a "switch", so a scene boolean attribute will do the job, called Spawnfinished or something.

For all of my high scores, I have an attribute which holds the value of each score. Anytime the score is changed, I call the "Change Attribute" behavior and then I save the new valu

attribute aliencount = 0

By "positioning them in place when they are "found" i.e when a certain boolean attribute is true" - do you recommend doing this by changing color alpha to 1/0? Or M

i.e when a certain boolean attribute is true - and put back when they are used. This seems like it would take up extra file size, but in fact it doesn't, only the first set does. Bit of a sketchy ex

Make a rule that says if the attribute scene.time is < 5 and char overlaps or collides with area change an integer attribute (lets call it sound) to 1. Then mAke another char rule that says th

Add 100 points to score attribute

except when I'm having the fade in and out actor constrain to the camera actor it lags behind and you see the edges of the screen showing through. So my thought was maybe I could make one large actor

except when I'm having the fade in and out actor constrain to the camera actor it lags behind and you see the edges of the screen showing through. So my thought was maybe I could make one large actor