It would go something like this. Have self attributes in each pieces that have the correct x and y positions. So correctx set to the right x, and correcty set to the right y

The camera origin is constrained x and y to an attribute.

Interpolate to a real attribute. Change the real attribute depending on the distance between the touch & actor using some math (Image)

create two game real number attributes and from inside the circular actor constrain the new game attributes to the actor x and y. You can the in the outer B objects constrain their positions to the ga

Timer after 3 sec. or whatever time change attribute finished level to 2

I don't know exactly how tshirtbooth did it but he might have had an attribute for each level and then when a block was destroyed it would subtract one from that attribute then when that attribute his

when destroyed=0 change attribute spawnbutton to true then when the person presses any button change the spawn button to false

I had similar problems with panning large images as part of a very large background. First thing I would test is to change the scene background colour to see if you are seeing a gap or a glitch. If th

okay thanks do i have to make a no stars collected attribute for each level?

If you constrain 2 game real number attribute to the ball actor's x and y, then in the second actor constrain it's x and y position to those game attribute, and then put a camera control behaviour in

make a game attribute: starscollected

I guess the attributes get an id which isn't changed in different instances of the same actor.

Yes, it does make sense - and is a variation on what I have been doing. The problem seems to be that as soon as you have multiple images all checking for multiple attribute conditions, the whole thing

Hmm well I am fairly new to gamesalad so not really sure, but I just had an idea for how to create this 'grid' system. For example say you want a 100 square grid, you could make 2 game attributes call

- The two long actors are LeftCenter and Right, they are constrained to Stretched arrow and are used as a "line of sight".

Does anyone else have this issue right now? If so then I can at least attribute it to the servers and not waste my time trying to mess with provision profiles etc.

After thinking about it a bit I figured it out. I just used an attribute switch to change the artwork to another image when the scene begins.

How would you make it so that a slider remembers it's position after going to a different scene? I followed Firemaplegames volume slider example but when I go to a different scene then come back its i

How would you make it so that an object (e.g a boulder) is always was behind the main character (e.g a stickman) even when he loops around (wraps with attributes (self position x)) but not when someth

When they collide, Constrain actor A's X and Y position to those of actor B. It will stick to it. You can do an offset by constraining to X+10, for example.