game, it'll be making a difference. Dropping constraints and replacing them with loops is entirely pointless.

I agree completely, and the only alternative I came up with involved the use of those 0 second timers. Since all they do is slightly delay the execution of the logic, rather than adding more condition

means it's spending most of its time idle with a constrain whirling away in the background busy doing nothing most of the time except eating up processor power . . . and when you have a large digit s

Looks like it's not so much a bug as one of those rare cases where order of execution actually matters. If you force the update of the self attribute to wait until after everything is finished in that

Cheers for the input BBEnk, yes a timer will make it work, but the goal is actually to avoid using a timer or constrain or anything more taxing that a simple one shot change attribute behaviour (in fa

Great observation! Constrain is always better for stuff like this.

* change attribute score (score = table value (self.time)*5).

'change attribute' self.score check to game.score

I'm hesitant to give away information that exists in a for-sale template because if it were my template I'd be upset if someone else did the same. But since you're asking for a single mechanic and no

You can interpolate the length of the stick, or constrain the length to an attribute.

(Quote)

The ball is now moved by the "move" behavior: Direction = self.rotation. Speed = BallSpeed.Game Attribute. There is no gravity or friction issue in the game.

I spawn an actor (A), and constrain its X/Y to an actor (B) that moves around the scene. I want a global attribute to change to 'false' if the spawned actor (A) collides with a wall actor (C) and to b

Under scene attribute, I have width as 768 & H: as 1024. Then in camera section I have same settings.

* Is the a way to make a condition that changes an attribute and when it comletes it changes it back or to something else ?

I am not sure what the issue but I was given the impression that when you add the play music attribute on first scene attached to an actor and when you switch scene, the music will still continue. But

The only other logic that comes to my mind is - when music 1 plays, then mute all other sounds. I only see stop music attribute but no stop sound.

Okay, what I ended up doing was making an actor attribute on my block prototype, an integer call "My X Position" I then put a rule on my blocks to change "My X Position&

Hi, thanks for the response. I had already tried the stop attribute, it just stops the sound completely even while actors are been spawn.

When attribute game.sound=1