I don't know but I can tell you how I did: I did a pseudo-boolean attribute needed to be true, together with mouse button pressure, for the base-layer buttons to work. When the new layer pops out, it

Make a global boolean game attribute called something like "busy". Set it initially to false.

Just wondering if I constrain a rectangle between two wheels would they be able to spin freely? or would they just be jammed to the rectangle?

Hi Falcon80; although the Interpolate behaviour is excellent and useful for many things, it sounds like, in this instance, that you're complicating the Rules unecessarily. By the sound of what you wan

OK. I found out how to do it. I should interpolate the rotation attribute from 0 to 360 and set a rule to start the interpolation when rotation = 0.

How can i achieve this effect? I tried to use interpolate on the actor's rotation attribute but it will only rotate it for one cycle (0 - 359).

To see if its changing the attribute or not You can make make a plain actor drag the display text behavior and choose attribute self.counter to be displayed. Then drag it in your scene and preview so

I tried making an actor and giving it an integer attribute called counter and setting to 10.

You make a real attribute call it player paddlex. Constrain that attribute to the position of your paddle onscreen. Then in the computer paddle actor you constrain self position x to player paddle x.

Also ... perhaps if you are controlling the moving actor you will need to turn off that attribute if you then direct it to move along and off the platform.

its linear velocity X to an attribute and then I constrained the following actors self.linear.velocityX to that attribute.

Whoops: in the first Otherwise section, you can delete "Change Attribute game.Playing to true".

change attribute Game.SoundOFF to false

to stop this if you need to, make a game boolean attribute called NoFire, for instance. Added to the When Touch is pressed Rule, put when game.Nofire is true, making sure All conditions are valid is

What scitunes wrote is true: too many constraints will cause you problems. You may want to investigate his suggestion:scitunes said:

I had that problem too.. I ended up creating several attributes to "track" whether the high score was processed. Here's a rundown of how it works:

I wrote in a pause functionality into my games by creating a pause attribute and wrapping any actors that need to pause in a rule that the pause attribute has to be false for their movement to work (o

I am trying interpolate with an "ease in" to the change and then triggering the scene changed based on the attribute. It seems to be working on the preview I've got 25 more buttons t

Hang on, get what you mean now; if it's done quickly. A workaround would be to have a boolean attribute called, perhaps, PartSwitch.

I started making a shark shooter game a few months ago, which I've kind of lost my way with, but I had a similar setup on that, didn't spawn just had 8 bullets and an attribute to cycle through, when