2. created boolean game attribute called beamOn

I'd check to make sure that the lives attribute actually has a value of 0. Sometimes, because of how the code is set up, the attributes can get out of whack and subtract more than one or even skip ove

Change Attribute Self.Motion.Linear Velocity.X to [something else not 0]

that actor to spawn another actor when some attribute (e.g. boolean) changes value.

My solution relies on attributes. First create two global real attributes, I'll call them Spawn_X and Spawn_Y. Then constrain the Spawn_X attribute to the X position of the HUD item, relative to the s

Wow this is awesome! I never knew tables could be used like this. In this way can I store any other attribute specific to the particular platform. Like if I want to have a boolean attribute to check i

I have an actor called platform. I have added several copies of it into the scene. The platforms are continuously moving horizontally. Setting a game attribute to keep track of the X position of the p

remove the move behavior and insert change attribute behavior.

To add to that, your HUD actors on an unscrollable layer do not need any constrain behaviors or anything else to keep them in place. By unchecking that box, they will stay wherever you placed them on

"The value 'xAH8Z0tvtD.[GameName]' of attribute 'id' on element 'tizen:application' is not valid with respect to its type, 'applicationIdType'."

Here is my attempted rule at "constraining" (however that function works...) the *jump button* to the camera (or "screen"?)

     Change attribute game.clicks to game.clicks+1

Change attribute : self.size.height to self.size.height +20.

Hi @GamePizza What the other guys said, but just to make it a bit clearer for you -for your table entries, make 3 columns, all real as attribute types for your red green and blue values.

     Constrain self.Position.X to game.Mouse.Position.X

What I need to happen is I need a way to have the user be able to manipulate this actor's position on the screen. Essentially, the user is dragging a square actor around. How can you constrain two att

What you need is to put those behaviors inside of an every 0 seconds timer. That will constrain the expression values to the CURRENT values of the game attributes you are referencing.

* Store the random number in an attribute so that you can delete the row from the copy table. This will stop the word coming up again in the same game.

@TaoOfSalad Some behaviours were not picked up by the tizen engine when I packaged my widget like the change attribute for self.size.width and self.size.height in addition to rotate to position ... As

(Quote)