you can look at fmg's circle rotate demo that has te exact movement of a volume dial. Then depending on the circles rotation you change a attribute between 0 and 1 that has the audio volume constraine

if you are using something like the scrolling thing in TSB's cookbook video you could constrain a game attribute to the speed of the cam actor and then make your buttons only work when the velocity is

Post a screenshot of your rules so I can look. If you have it changing something to true for example, have when touch is pressed AND blah-blah is false then change attribute blah-blah to true.

Haha fair point, make an attribute lol. I was super rushed when I put this, I was trying to see if he had made one as a few newbies get confused with creating them and 'swipe direction' is an attribut

Fair enough Ace, I don't doubt that you can but I'm just calling it as I see it. Lot of that going round. "Make an attribute" :P

The swipe direction on the video is an attribute if I remember correctly, that's why I was making sure he had an attribute.

Thats a good problem list. Only other thing...is dis-link between actor and prototype, make sure both have the attribute especially if you are destroying and spawning to change level!

2 global attributes touch & release

You have to make an attribute.

well you change self color alpha from 1 to 0 anytime in the game or before to change between visible and invisible. The actually visible attribute under its graphics attributs cannot be changed though

I'm especially surprised that visible cannot be changed. It's also a bit strange that change attribute let you change it.

I didn't want to kill the bullets/missiles too quickly, as it didn't sound or look right to see something suddenly disappear. So, I created a "dud" system. If the actor crossed the e

I believe I used the text attribute method because I wanted to use spaces in between words and I couldn't get it working with just the ".." method. For example, I wanted something l

i did the change attribute just now and it did nothing

The core of the problem was because I didn't know Change Attribute was a once only action. Problem is fixed now, thank you very much for additionnal informations tenrdrmer.

You can either use another actor that they overlap outside the bottom screen to trigger an event or set the attribute to y< (bottom position number) then changeY to top positionnumber type of t

I haven't got access to this camera attribute.

Did you put a collide attribute in the ball?

Like Constrain Attribute game.offset.x to game.camera.origin.x

If attribute 1= play sound (whatever sound you imported)