Attribute called onoff.

Can't you just have an attribute per everything you need to play in a playback? Assign an attribute per whatever second of recorded sound or so and bingo :P

`when attribute game.level = 1 ...`

You'll need to create an attribute (real) and set it to 30.

When you create the powerUpScore attribute, initialize it to be 1 instead of 0.

Constrain Attribute

In the spawner actor, create an integer attribute called something like "powerUpScore".

Pixel Collision would be nice... but I would like to go timer, constrain and graphic crazy without it slowing down to a crawl first...

In the spawner actor, create an integer attribute called "randomNumber".

yes...interpolate alpha in the color settings for a nice fade up.. don't forget to set alpha to 0 either with a change attribute first or in the main attribute settings.

IF attribute 'reset' is true

In the spawner actor, create an integer attribute called something like "powerUpScore".

To access the Camera, you need to have an unlocked Instance. Instances in the Scene have full access to the Scene Attributes, including all the other Instances in the Scene.

You would use them to check for collisions between different objects.

Constrain self.position.x to:

Instead of just having a collision event, could there be a behavior or attribute that you can use to check if there is a collision between objects?

Could you constrain your buckets to x,y points on the wheel actor?

So I created this attribute as a separate rule. Should I have incorporated it into my movement rule? (see image above)

- I created a game boolean attribute (Walking)

We removed the collisions and still had memory problems. I too have found problems in both adHoc and viewer.