As long as you have a "Load Attribute" on your menu or wherever you want it loaded. Yes it does work on the device.

1. When attribute self.color.alpha = 0 reset scene

I think I posted this in your other thread, but try constrain attribute self.image to ceil((game.direction*10)/2)..".png" and rename the images 1,2,3,4 etc...

Can game.direction only = 0.2 or 0.4 etc? If so change the image names to 0.2, 0.4, 0.6 etc and constrain self.image to game.direction..".png"

when attribute game.direction = 0,2{

I think TshirtBooth's tutorial doesn't take in consideration one problem for gamesalad: the collisions will not zoom out but only the image.

This may be a silly question as I have yet to test my App on a physical device but do the global game attributes get saved. So on the phone if the player reaches Level 10 and I save this into an attr

make an attribute positionX = self.position.X (so if you're actor is called actor1 = actor1.Position.X) this is his x coordinate of actor1. do this also with positionY.

This can be done easily if theres array in GS as you can actually iterate through the array to check. It can be done in GS but it's a bit tricky as you need to set an attribute on each location on the

So basically you want to know if there is an actor in a certain point and you want an attribute to remember this. I assume so it won't spawn another actor in a position that is already filled?

I need some help with collision detection. I have a ship the moves from left to right and back when you touch it. The ship has a collide attribute to bounce against the wall. The wall has the same att

Put the collide behaviors in both actors' rules. Also, under the GRAPHICS attribute in your wall, uncheck Visible. That way, the player won't see a giant, impenetrable wall; only that the character ca

If score < 0, change attribute self.color.alpha to 1

make a boolean attribute called shoot.

If it's moving, then you can constrain the particle actor to the car actor.

You can create a real self attribute named something like "HowFarAway"

The problem I see is that it is working fast. Since your rule changes the condition state of the attribute check, it immediately sees that it should execute the behaviors in the Otherwise section.

If I create 2 actor (ball and wall) and an attribute, then I create a rule, in the wall, like this:

I've not come across an attribute or direct way for it but you could create a new tag and put every actor in it. Then on the actor create a rule that when actor overlaps or collides with actor of tag

make an attribute collide