If you double-click on the invisible collision Actor that is in the Scene, and click the padlock to unlock it, you will now have access in the expression editor to Scene Attributes, among them the Cam

Change Attribute:

thinking and thats how we come to some of our attribute chains.

This Actor Instance sits just offscreen and resets the level Attributes. Stuff like:

But now, when I return to the sceen (again using a new unpause actor with a simple ..resume music and change scene...rule) most (but not all) of my actor behaviours do not work...these include &qu

Spawn, destroy, a change size timed attribute, maybe more....movement rules seem unaffected.

ORBZ, try using tags instead of actor names to determine your collisions/overlaps. From my testing, it looks like the update has messed up the use of actor names for this functionality.

Well I found that constraining an attribute to itself minus an amount does not work anymore.

Easy Way: Create an invisible actor that is just a bit bigger than the screen. Then Constrain its x and Y to the actor that controls the camera. Then in the moving objects you want to control you put

@Eastbound, Trying to discourage using Constrain Attribute like that to increment itself. Try a Timer with Change Attribute combo.

loving the return on attribute, such a handy feature that used to annoy me not performing like it now does. Woo

- When adding a new attribute you can now press enter to add it instead of clicking only on the "Choose" button (a big time saver for me)

Hmmm, just deleted the (bool) attribute and the action and re-added them and it's working fine again!

You need to use an integer Attribute. When you click the plus sign to add Attributes, make sure you choose Integer.

First, create a new boolean Attribute in the Actor called 'destroyMe'

JGary321 came up with this neat trick on using a Change Attribute Action for images: http://gamesalad.com/forums/topic.php?id=2939

yes, you will need to create global game attributes that hold all of those properties...

you have to setup all the values you want to transfer in the game attributes area; speed/velocity, angle of velocity, size, position x/y etc. then you will have to either constrain these values to you

what i had to do was create actors on screen that showed attributes that i was tracking to check the 'try again' or 'you win' situations. sort of like debugging. each collision was supposed to registe

The "Collide" behavior doesn't seem to be working on the iPhone/iPod Touch with 0.8.1. When I preview the game in Gamesalad, the collisions work correctly. However, when I publish th