so we have a game attribute game.Quality.

Ok , im sorry for all those comments but i am trying to do the same like you did and i cant find the Scene option on the constrain attribute behavior , i only have : game , devices , services , actorn

I have an in app purchase menu and when the user presses back to return to the main menu it saves the consumable iap

Game attribute:

Hey guys, so, the problem that I have is this: when my character is running, he is supposed to jump over the flying obstacles. when he hits one it destroys him. however, in the game it doesn't work. …

Hey guys, I am currently working on a school project that requires actors snapping to another actor, I have the base of it working but when I duplicate the rule of one actor "actor_a&quot

I agree that the crash rate is unexpectedly high. Though for me, the crashes seem to occur when assigning an attribute from the selection box thingy if I have a lot of commands visible and haven't sav

(Quote)

As an example, if you have a rule that says When attribute game.score > 100 spawn an actor, it will trigger when the score goes from 0 to 150 but it will not trigger again when the score goes

As the ball will automatically inherit the spawner's rotation you don't really need the constrain behaviour in the arrow, nor do you really need the attribute that passes the arrow's angle to the ball

Integer Game Attribute called: gameSpeed

I've tried making a real attribute and then to make an timer that say that every 5 second the spawning will be "attribute" plus 20 and it didn't work !

Do you think I'd need an attribute to make it work?

A spawner actor located outside the scene is spawning enemies, which after being touched change attribute Combo to Combo +1, and after missed, reset Combo to 0.

(Quote)

change attribute

Make an invisible actor. Ad rule if mouse button is down change attribute of actor x and y to mouse x and y (where your finger is). Have your hero actor then move towards that position. One thought al

Make Game Attribute: Arrow Direction. Make it an angle type.

For Question 1, i recommend adding a Touched attribute to each box, and mark the behavior that moves the score up 1 to require the touched to be false and to set the touched to be true. that way, each

* Create a self (boolean) attribute in the box actor called HasBeenClicked.