That'd fade it, though. I think he wants it to flash. For fading, could also use the method I put up there and swap out CHANGE ATTRIBUTE for INTERPOLATE, the less rules and attributes, the better.

Hehe, I had this the other day. I was screaming for hours. It was a lost attribute.

First make a fade in boolean attribute in your actor that you want to flash. Name it "fadein"

Also, instead of using an invisible actor for detection, you could have an attribute named "Detectable" and have it to switch on and off. When it's on, the player's touch counts, whe

It's got to be a "dangling attribute"

WHEN alpha=0, AFTER 1 sec, Change Attribute self.alpha to 1

Yeah, use a timer - "EVERY 1 second, FOR 1 second, CHANGE ATTRIBUTE self.alpha to 0". Or something like that... not sure if that would work... brain is a little fried right now... 4:

Would that be a 'Change Attribute' inside of a 'Timer' behavior?

You could use timers to change the self.alpha attribute.Not in front of GS right now (at work) and I'm so tired I couldn't tell you how to do it without looking inside GS but at least it's a place to

change the scene gravity as gravity is a scene attribute. There is also a way to make that rule work in your prototype even though you will be told it cannot be done by this forum. The problem is onc

Hello, could you explain to me the differences between attribute types (boolean, text, integer, real, angle and index)? Which of them is better for some actions, or what are the pros and cons of each

Then put a Change Attribute behavior in the spawned Actor, like this:

Try having a new attribute called direction, Then in the rule which controls the movement for left have it set attribute to 0, and the rule right to 1.

use FMG's circle constrain demo so you can't pull down past a certain point. I use it on my ANgry birds style levels on my current project.

When you attempt to drag an attribute definition (blue pill box in the expression of the behavior) to another behavior - sometimes its easy...but most of the time it isn't.

When I create an actor with a set of rules and custom attributes and then insert it into the scene(s). Then later if I make a clone of that actor in the actor library - rename it...then go into it an

when attribute is > 240

In the Game Attributes, there is an attribute already set for music volume and sound volume. If you intend to use this, you will have to use the attribute in your "play sound" and &a

you could modify codemonkey's joystick demo. The idea is that you have 5 touch actors that constrain to touch 1, touch 2, etc. (look at his demo and you'll see what I mean - it's a bit complex). But t

When attribute is above 240 change state to 1