For example: Say you wanted to use IF NOT X then do Y. What you would do is create a boolean attribute (game, scene, or actor depending on your needs) called "X is True/False." T

to get rid of the bounce change the resitution to 0 on the actors. Its under there physics attribute

Have your attribute called musicOff and have it set to 0

When I save attributes for my game, boolean attributes and integer attributes save and load back in fine. But when I save a TEXT attribute, it doesn't work. Not sure if it's not loading or saving prop

It's a weakness of GameSalad — Custom collisions shapes are not supported. Additionally, the radius of a collision shape (circle/square) cannot be specified.

So far I've just been constraining an larger image actor over the "hit box" actor. Is there a better way ? how many things can i constrain before bad stuff happens ?

One possible idea... check the attribute value with the new GameSalad debugger. The data displayed in a GameSalad game might be different than what's actually stored.

Basically, I have a boolean game attribute called resetting. When the fireball explodes, or the level is reset, the game.resetting attribute is changed to true. Actors in the scene (by using rules) ac

timer every 1(or whatever) seconds change attribute spawn order to (spawn order +1)%3 .. so spawn order cycles between the numbers 0,1,2 then back to 0,1,2 and so on... then in your actor tell it if

try constrain self.rotation to vector to Angle (self.motion.linearvelocity x,self.motion.linearvelocity. y)

I don't think that is possible. I would love to have custom collisions though.

try constrain self.rotation to vector to Angle (self.motion.linearvelocity x,self.motion.linearvelocity. y)

Great demo.... was wondering if we can accessed any particular "array" from the text attribute? It will be awesome if I can grab the data during the game...

I need an attribute to be increased by 1 when a timer reaches a certain time but only when the attribute is smaller then 3.

I think you make an actor attribute and then every time an actor is spawned that attribute is only for that actor. so if you have an actor called soldier and under that actor you add an attribute cal

on screen. Would I need to have a separate attribute for EVERY actor? Is there some easy way to handle things such as these yet?

The collide attribute is with the block so its that easy.

If the collide is in the ball you will need a game attribute, when the blocks go to alpha 0 they will need to change this game attribute, when they are back at alpha 1 you switch the game attribute ba

I have the vanishing part working by changing "alpha" to "0" and have made it change the score attribute when hit. I also have the reappearing after the timer worki

but spwan attribute will affect performance