I dont know if "x-scale" is actually an attribute (probably not), you have to actually locate the right attribute in Gamesalad.

Select the cards width attribute from the drop down in the expression editor. Theres no scale attribute its width and height, and you cant just type them in you ahve to select it

if card is clicked, then interpolate the card's attribute X-scale to 0 over .5 seconds.

if card is clicked, then interpolate the card's attribute X-scale to 0 over .5 seconds.

when you say 'drag your flipping animation sequence inside of the animate attribute', is this something I'll have to create in Photoshop or After Effects? What should I export it as?

Also, if you didn't want to use the animate attribute...I found this that might be helpful to you:

I would use the animate attribute.

If you want two actors to communicate you need a Scene-level Attribute. One actor changes the attribute, and the other actor has a rule -if the attribute is changed, then move to wherever. Make sense

to make a line/strip as a ramp … change its Rotation attribute

Global attributes:

well integerAttributes store numbers without decimalValues …

gameAttribute: boolean … name: wheelRotate

These 4 boxes have the same math expression. The boxes on the left use a Real attribute, the boxes on the right use Integer. The ones on the top do not use FLOOR, the ones in the bottom use FLOOR (aga

To have it to rotate during collisions let the fixed rotation option unchecked. If you want the wheel to have a specific rotation you could add a rotate behavior to a collision rule.

change attribute.self.position.y to random (0-640), what expression do I need to add to exclude y (300 to 340)?

Generally, if you want to reset an actor's attribute, you do the following:

constrain velocity.x to 0

I think with a change attribute it will start to shake again. I would just go with the constrain, it won't hurt performance very much, you can get quite a few in before you notice any drops

I have that same concept but the linear.velocity not as a constrain but as a change atrib. Any differences in this case? Yes, I avoid constains at all causes.

----Constrain self.linear.velocityX to 0