Started doing the way you've said, just checking where you say to use trig to constrain....

elevate the block's x,y to game attributes.

In the block actor, constrain those global attributes to self.PositionX and self.PositionY

I've tried using the 'position x and y' in the spawn attribute, but that only makes the spawned actor appear in the right place when spawned.

Bug/Issue - Overlap / Collide rule doesn't work when actor size is constrained.

you tap into them. You shouldn't need to use constrained behaviors to utilize them...since they are already constrains in a sense and are running in real time.

I just meant in addition each actor also has its own timer separate from adding a "timer" into it. So you can get a way with using that to change an attribute so that you can have a

I need to change colors by click and it works with the standard colors, but when I try to make orange, which has the green value of 0,xxxxx and I make a "change attribute green to 0,xxx&q

you have to spawn an actor and use its self time that works just like the game timer then you can destroy or re spawn to start and stop. Problem is you of course have to constrain it.

1) create an integer attribute in the actor called "markGameTime". This will be where you store a "grab" of the game time to use as a benchmark.

The change attribute (self.Tags) didn't work?

Makes it nice to just resize up and constrain the proportions on the styles.

Can you tell me how??? So far I've gotten Rule, then Attribute: Devices: touch 1, then I did them both x and y to in(x) and in(y) but now neither of the buttons work.

What attribute would I need to be able to set it so its not a defined pattern which repeats itself.

If I use angletovector and change the rotate attribute by this number, it works somehow, but it is not good.

Having a strange problem. I have a countdown attribute "timer". I have 2 buttons to set the time either minus 200 or plus 200 to the main timer - so if the timer is set to 500 and I

Create a global game attribute (integer) called something like squarePosition.

Now I have actors on the background layer and they have rules and use attributes of course and they worked all great.

Ok first make a new boolean attribute in the game attribute section named say, 3GS and set it to true. True being the iphone is a 3GS model, false being it is not.

Without drag...there is nothing to slow your actor down except collisions. With drag...it will eventually slow down...like billiards balls after a strike on a table. The collisions will reduce the a