Pretty much as you suggest. I would throw a random number between 1 and 100 perhaps for each attribute and then if there was a repeat make a repeat of the loop. Then select the highest with a >

Doesn't it sound strange that setting one integer attribute (flying) is causing an accelerate behavior not to fire?

When the attribute which triggers the fire power-up is true, make the attribute for the ice power-up false; and vice versa. Fingers crossed that'll sort it for you.

up to add points (up to a limit) to an integer attribute based on a timer set at 'every' (enter the time element for each point addition). So it might read something like-

Basically I have a fire power-up and an ice power-up with an attribute each.

How do I make a hold to charge attribute? One simple example then I can work out the rest.

ChessPawn said:Maybe I meant it switches the attribute too fast for the gravity. :P

Sorry about that! Okay. So under the list of behaviours you used for any actor in you main scene you create a rule that says if the attribute (your boolean attribute) = false then drag both a timer, a

Make an boolean attribute set to false. Then create a rule: attribute =false then play music the after 1 second change the attribute to true Then under the same rule put otherwise continue music.

when pressed change attribute to 1. have another rule when release change attribute to 0

I don't know why I can't figure this out, but I have an actor, and when I touch that actor, I want it to change a self attribute to 1. I then want that self attribute to go back to 0 when I let go. I

add a behavior to the actor change attribute game.device.musicvolume to 1

I don't know why I wrote "too fast." What I mean is that, it still doesn't recognize the gravity. Maybe I meant it switches the attribute too fast for the gravity. :P

Go into your actor and under the Graphics attribute group, change the horizontal wrap and vertical wrap to stretch rather than fixed or tile.

First way: Create a game attribute and use constraint to actor1 Y and then in actor2 use constraint again to constrain actor2 Y to the game attribute you created.

So for my game I created an integer attributes and set it to one. and everytime a level is completed the attribute increase by 1. in the level actor I created rule for each level, for example for leve

Yes i did but in t shirt booths video in the movable character he adds a +camx to the constrain attribrute.But it doesent work on my drageable image. and is that your game? it looks pretty good iam go

there is a video from tshirtbooth on the cookbook youtube that shows howto set up a custom attribute called power and base it on the distance of the touch input from the cannon.

there is a video from tshirtbooth on the cookbook youtube that shows howto set up a custom attribute called power and base it on the distance of the touch input from the cannon.

Create a scene attribute (integer), for example BadGuy01Speed, something say like 200.