(The attribute below is put above the otherwise in the grey box)

so you have an attribute, "scene number"

The only thing not working is that random number now in my change attribute... I tried a function of "random(1,5)" and that does nothing except go to one scene however when I have ju

Becuase the attribute is picking a random number, hence the scene picked will be random.

Create an attribute (integer) for your scene, call it sceneselector, use the change attribute command to change sceneselector to a random number.

How many attribute can you create until a game get a considerable slowdown? And how they will impact on load times?

You might also want to make a global boolean attribute just to lock it down like this:

These are the attributes for the buttons and the actor

I have a bomb-type actor that explodes several smaller actors out of it when triggered. These smaller actors collide with elements in the scene. With one 'bomb' spawned on the stage, the exploding a

this doesn't work for me either.. not even to spawn just create a random value in an attribute and then displaying in an object (Image)

I have an attribute called "game paused".

Use two Change Attributes to kill the player's motion, like this:

You know how the background attributes of your scene, it has an attribute called, "Display Size"

Add to this, you can then create overlay actors that you constrain position wise on the top of the aforementioned monochrome actor. This has the effect of adding more color, features, clothes, armor,

It's an easy way to set limits on things - the second choice is usually the max limit of the attribute you're tracking.

are you using touch to control the player paddle? Any tips for doing that that I can use on my kidney bounce science game? Did you just constrain the x position to touch?

If all of the actors are very different you could have an actor for each and an integer game attribute called playerID or something. Then in the spawner have 40 rules. When game.playerID = 1 spawn pla

I would create a game attribute (integer) called ballX. In the ball constrain game.ballX to self.positionX

Just remember to implement a game boolean attribute "SceneInitiated" to test for before doing other things otherwise you may get unexpected results (i.e the initiatation should of co

It would make the Computer Paddle move in normal speed and in the direction based on whether or not the Y values were higher or lower. I knew Constraining the Attribute would make the Computer Paddle