@Phoenix256 make an integer self attribute , call it switch ,

I don't mind how the GS business gets structured as long as we start getting engine upgrades at a faster pace like Google Play services, custom fonts, (at least semi) custom poly collisions, and joint

Absolutely, a game attribute will do exactly what you need.

Is it possible to toggle on/off all sound effects at once? Maybe something like a game attribute, in apposition to individual self attributes per actor?

Is there a touch attribute in gamesalad? I have blocks spawning randomly but I don't want them to touch, how can I do this?

The way I shuffle is to pull a random number from 1-52 and have the change attribute show that image from the Column 4.

Yeah, basically you construct a 'straw man' (an argument that is comically easy to push over, like a man made of straw) and you attribute it to the person you are debating/arguing with - usually as a

(Quote)

When you stop tapping, reduce the speed using the game attribute. An interpolate to 0 is probably going to be best, but it depends on how you want the actor to slow down.

So would need an objectdistance and positionX and positionY attribute for each enemy...

I have my game set up like this When main actor collides with Star DO: change attribute game.star score to game.star score +1 & Destroy. Sometimes when the main actor collides with the star ac

Hey I did it! I can't upload the project, so I'll give you the code here. But, first you need a table, a single actor and 8 attributes titled:

Wow it's a very great news! and i hope that this new policy bring GS more great features like multiple objects selections, joints,collisions editor etc etc...

that trails behind the asteroids using a game attribute I created called "Ytracker." I just add enough space to the Ytracker in order to make sure it does not touch the asteroid it

Another is to constrain the x and y position of the square. This isn't always entirely reliable, though.

I don't think loading 20 attributes at one time is a problem. I sometimes have many more than that. It makes sense to load in all of your attribute before the data is required - saving attributes is u

Then make a boolean game attribute (true or false is why its a boolean)

i suspect you are tracking them all together as they are the same actor and you have them reporting to one set of attributes? If so that's not going to work. If all you want to happen is something to

@The_Gamesalad_Guru What do you mean by "separate all the actors"? & I switched the actors constrain & rules around like you said. So now what was in the Enemy Actor

@frd I thought the same thing as well. But when saving/loading other attributes, such as an in app purchase, then closing/reopening the GS Viewer, my purchased attribute was saved...