i would try creating a attribute in each of the 3 placed actors on the scene. name it "size"

You'll want to use two things in the expression editor. VectorToAngle and magnitude. If you constrain two game integer attributes to the bomb's X and Y you can use these in the block actor to get the

To add to this, to start music on my splash screen and keep it playing everywhere in the game, I created a global integer attribute called playMusic defaulting to a value of 0, then had the splash scr

You are using a touch on an actor that sets a game attribute that is read by the player.

If this is not feasible, at least provide some attribute that could determine if the actor is actually on top vs. not.

I create an actor attribute called, self.whoami

I am not sure, but maybe if you have a game.attribute.count for example, on your spawner for every object that you instance you can increment first the game.count and inside the actor you can set a se

Personally I would have them look the same but give them different actor names then depending on your condition ex. Touch actor 2 in scene 1 Change game attribute to 1 so in scene 2 when game attrib

A time, based on a game attribute in a prior scene. I want to be able to fade any of the four, based upon an earlier selection.

Oh I see! That's what constrain attribute does...

Use constrain attribute only without a timer.

Thanks cat! but now when the ball falls and hits those actors it collides with each actor moving them... When I uncheck the "movable" attribute for the actors then I can no longer co

is, if it is moved into place, it could detect collisions and if spawned into place, overlaps may not be sensed if I recall. So you would have to grow it from one actor to the next - performance wis

At the place where you "pick the examples randomly", try putting in an "After" timer with a duration of 0.5 seconds. Then, drag the Change Attribute box where you &

change attribute clickmanager value 0

Create a global game attribute called CameraY.

- So integer attributes for Lilypad1x and Lilypad1y.

A Real attribute is supposed to have decimal numbers. However, when I try to display a real attribute, only two decimal places are shown.

so what most people do is create two game attributes called cameraOffsetX and cameraOffsetY (both reals)

and another called lillypad1y. In lillypad1 constrain lillypad1x to self.positionX and constrain Lillypad1y to self.PositionY. Then have a Boolean game attribute called jumptopad1.