Rule# 2 ( when actor receives event : touch is released : change attribute game.Score To: game.Score+1 )

i have a timer. every 1 sec, change attribute, game.score to: +1.

I'm seeing references to "Tizen Back Button" but I'm not getting a clear understanding of it. It looks like in order to constrain the Hardware Back button to scene navigation, you ne

* constrain self.position.x to mouse.position x

Change Attribute JodyMitoma.eyesClosed to True.

The actors themselves should have a Touch command with two Constrain Attribute behaviors. One to constrain the object's X position to the Mouse X position, and then another to constrain the object's Y

Im constrain.self to sleep soon

(Quote)

If you refer to changing your clothes as "Change Attribute Self.Image".

I recommend creating a new attribute. Make it "upgrade number". Have it be wrapped into the cost number. (attribute cookies > (Upgradenumber x 10)) for example, would make it

My movement set is using Constrain Attribute(velocity) commands to control the speed of the player hwen the keys are pressed and unpressed. it detects the bottom of the floor using a small bounded box

* Trying to interpolate Play Music attribute to fade in/out simply does not work. Only Play Sound will fade in/out.

@SquareHeart‌ , constrains do usually (and always have) break collide rules. Try to achieve the same pulse effect with an "every 0 second" timer and change attribute behaviours.

If you find yourself wanting to add a Constrain behavior to your cat.

Collide behaviour itself wasn't affected, but rules triggered by collisions stopped functioning when I applied a constrain on the X and Y of the Player Actor (constrained to sin - object gently pulses

use table, its better than save attribute

If you change an attribute to random (the attribute, 10) - it will bring the lower level up with each iteration.

I tried using the current state of the attribute, and that didn't work. Ex," game.roll1 = random(game.Roll1, 10)" was still dropping below the 'current' roll value. I was impressed

Yup. Different behavior (Load Attribute), same attribute (scorekey).

Thank you moik and Brayden_SFX for the fast reply. Last question is do I use the same "as" value when loading attribute?