(Quote)

Attributes (For whole game) Needed:

Yes! I placed a Change Attribute behavior inside a timer. I wanted to have the score reset every time I change scene.

Ignore the attribute named can.

I have an attribute called "lock" and it is a boolean set to true. I have it so when "lock" is true and "coins" is >/= 10 when touch is rel

What is a 'timed change attribute'? Do you mean you placed a Change Attribute behavior inside of a timer? What is the full name of the attribute you tried to change? In which actor of which scene d

What I've had to do is instead of using the embedded rule to change scene, I toggled a boolean attribute and then had a external rule that detects the toggle change to change the scene like so:

You make an actor - place a constrain behaviour in that actor - and then place the code in that constrain behaviour . . . . . remember to select 'self.time' and 'self.color.alpha' from the pulldown m

I made a timed change attribute of score to 0, still not working properly, what I am doing wrong?

Constrain self.color.alpha to 0.5 *sin(self.time *200)+0.5

Another way is to make an Index Attribute.

You could do 'RULE' then the collision or touch or key, 'Every=***' :do: 'Change Attribute=self.color.blue/green/red' :to: 'self.color.blue/green/red+0.01' .

(Quote)

@socks - That's a nice solution. I like the way you borrowed the angular drag attribute instead of making a new attribute.

(Quote)

Did you remember to manually set the attribute "stateRotation" to 1 ?

(Quote)

Make a new attribute for your actor (integer).

Using interpolate causes the engine not to detect collisions. If you're looking for that smooth movement that interpolate provides, you could look into using motion linear velocity instead.

Planning...make tons of notes...then re write them...make kind of a story board with all the attributes you want for each actor. I made a mistake of...after a month of lots of coding to add another f