Hi, I guess you're using an integer attribute, its value set to the amount of boxes on the screen? And on-screen but outside of the play/view area, an actor with When attribute CountDown (or whatever

Hi, make an integer attribute called EnemiesD, for example. Set it's value as the number of enemies there are. Put an actor outside of the play area in your scene, and in it's Rules, put:

Okay, so I am creating a game in which one of the functions of the game is that the user will drag and drop an actor into a box (which will be another actor), and when it enters the box, an attribute

I realize that GameSalad wants to protect developers from scary coding, but this approach actually creates more work. A single time attribute would be better for game development. Yodapollo said:

I'm trying to display a line of text that contains a game attribute. I want the line to read as follows:

If you didn't already, use 'change attribute: self.image' instead of using the 'change image' attribute. Also don't allocate actors with images but leave them as white squares. This can help with load

If you didn't already, use 'change attribute: self.image' instead of using the 'change image' attribute. Also don't allocate actors with images but leave them as white squares. This can help with load

Rule when attribute = whatever

Ok so I've noticed that using a touch is released and when attribute = whatever, GS tends to make the touch is released fire constantly until the attribute = whatever, instead of only activating the r

I'm not sure where i should put the save and load attributes.

By making a set of duplicate sounds, put - for each different sound - when bool. att. SoundX is false, play the first version, then change attribute to true; when SoundX is true, play the second versi

example, the "Display Size" attribute can be expanded by clicking the disclosure arrow next to it, revealing size and width attributes. I would like the ability to do this with cust

ok i found a fix for anyone who might see this again.. inside of each of the rules.. i created an additional change attribute that set the game.random_sound value back to 0... which is always out si

When your actor is pressed, spawn a second actor (with your second image) in the first actor's exact position. Make sure this second actor's alpha is set to 0. Make two integer attributes, let's call

Thanks, thats helpful... I think its just getting the hang of what gamesalad is actually doing under the hood. Each spawed rock was individually being destroyed by the bullets etc etc, but I had an ex

Yeah I did it with just one attribute but every time I reset the scene nothing seem to run, its kind of like the pause is still going but the menu gone and I have put an unpause behaviour in the pause

every random (random.time) seconds: spawn actor, change attribute (random.time) to random(2,6).

on touch rule, read the x and y value for actor.position attribute, and make a constrain attribute to that actor to this values. I never tested that, but i think that must run ok.

I want to be able to set a few actors in specific grid spots and have the game attribute that tracks each actor named "piece" (game.filledSlots) account for the coordinantes of the p

Now when I play SCENE 1 and my energy gets to zero i have an attribute (Boolean) called 'GAMEOVER', so I have it that when the energy bar gets to zero - change attribute GAMEOVER to TRUE.