You can do it with one attribute.

boss) + 6 stages still equals 180 attributes.

You can do it with one attribute.

I'm going to assume by drag, you actually mean constrain. Drag is a physics property in GS. If I'm wrong in my assumption then disregard what I'm about to say.

I have 4 different badguys(some rounds fight 1 of 1, some fight all 4, or 2 of 1 etc), 5 different fights over 6 different stages. After each 'wave' i need to tell the game to start the next wave in

Then constrain another invisible actor to the shark's x,y to act as the collider.

Couldn't you just encase a change attribute in a timer? Have a timer change the y position every .5 sec (or whatever works). I would think it would work like a "delayed constrain".

Hey guys, I got a question for you. In my TOTB 3 entry Break For It! I have a shark that constrains to the y position of the turtle. However I would like for it to have a little bit of a delay instead

ok so you have your 4 attribute'ss moveLeft moveUp moveRight moveDown

First, as far as I can tell, GameSalad's modulo function (the % operator) returns the sign of the second number and not the first. But for this purpose, we need the modulo operator to return the sign

Basically you save an attribute to a key at a given time in your game (called what ever you like)

How do you separate the touch and drag attribute apart from the touch and rotate on the same actor?

If I wanted to load say a attribute on startup, could I do this even though it is set to Scene Attribute or would it need to be link to the Game Attribute List?

But to remove a different actor when the first one dies, i need to make an game attribute to destroy it and put on that actor a 'destroy this actor'.

Apparently you dont need to make an adhoc build to test save/load attributes anymore.

if you just use the move attribute and make the speed accelerometer*(what ever number you want) it will bounce! promise! Because bouncing will still change the speed and it scales to how much tilt. id

the walls. This is an obvious problem with the constrain behavior, but how can I get around that?

Constrain self position x to : self.position.x-(game.accelerometer.y*17)

When attribute device accelerometer x >0.5 move right

Try upping the Drag and then also setup a rule that is when accelerometer y is less than a value constrain self.linearvelocity.y to (self.linearvelocity.y*0.9)