First off, you'll want to make a behavior so that when the actor is touched it changes the power attribute... you can do this a couple of ways, one being to constrain it to a graph or something like t

First, make two boolean game attributes called RedPressed and BluePressed.

(Quote)

send data values such as player names and attribute changes. I could be wrong but I believe those behaviors mainly access the data already stored on the game itself.

(Quote)

the value of any "important" attributes back to their original values. For example, if you have an attribute called game.questionAnswered or game.Start or something along those lin

IF attribute gameover = true

(Quote)

Hi Experts, i am stuck at the rule -"when self color is red, change game_color number to 1". How should i go about it? Create a self attribute with integer, text or else?

What I would do is create two game attributes. One integer attribute and call it something like color_number; then one boolean attribute and call it button_pressed.

On send change this bit of code to what rows you want in arrlength attribute

Hi everyone, just wanted some help with collisions, how would I make an actor disappear and respawn in a random place when colliding with another actor, like in the game snake. Also how would I make a

on that row in the table depending on their self.attribute "position" - which should be 1,2,3 and 4 (they should all be the same actor). The answer button that is position 1 is the

In the expression editor, game.End (circled above) has been typed in directly rather than selected from the attribute browser drop-down menu. You must select attributes... you can't just type them in

I woukd think that you must beusing three "when touched" attributes of some sort right?

deciding what language to use.Hint of Polygon Collisions and Joints and other things coming to Graphene. And now your saying in this meeting that they dont know what features are going to be in Graph

"if self.position.y is < -20 in the rule add a change attribute self.position.y to 400"

Then simply make a rule if self.position.y is < -20 in the rule add a change attribute self.position.y to 400 for e.g. you might have to change those numbers depending on device and portrait la

Make two 'real' attributes in an actor, call them something like swipeX and swipeY and a third 'angle' attribute, let's call that one 'swipeAngle'.

best for this unless you only have a couple of attributes to save, in which case you can just as easily use Save Attribute and Load Attribute behaviors. If you aren't familiar with tables, start by