I start the game out with attribute LEVELACTIVE boolean set to false. When you click the start button, the value is set to true. After 10 seconds the boolean for LEVELACTIVE is set to False. WHen t

If you want the actor to stop when touch is pressed, you can either use an attribute for the speed and use a Move behavior (to stop the actor, change the attribute to 0) or you can put the Move behavi

I Inserted a Change Attribute and changed the 'Change Attribute' part to self.Motion.Linear.Y to +10

create two global attributes:

how do i make a game attribute. when i make a new one it says self attribute

(Quote)

Change Attribute gamePoints to gamePoints + 10

Im trying to make a button control a actor/actors that increase a game attribute integer (game points) through booleans. I cant think of what i could have done wrong. it goes like this...

Make a boolean attribute, let's call it Loop, and an integer attribute, called Count.

If you however had a character that had excess room in the image that was just transparent and wanted the collisions to be more precise, this is how you would go about it.

When i press a button to change to a next scene in preview mode on my android device, the resolutions just messes up and everything are misplaced, and a part of the screen shifted to the left of the

The rule in A is set to whenever touch pressed, after 2 sec change the table value(the 3 rows boolean) into true, so that it can link up the attribute in B. B contrained its boolean with the boolean i

So for example, if you have an actor that moves from Y=-100 to Y=200 and back again to Y=-100, you would have a condition When attribute self.Position.Y=-100 --> Interpolate self.position.Y to

Ok so I have an attribute that is either 0 or 1 by pressing a button (my attribute+1)%2

Make an integer attribute, let's call it SpawnCount. The following example is for different rules for 5 spawned, obviously change the numbers accordingly for more or less.

So thinking about it, all that's left: if it works without the attribute condition, in other words, if it spawns as you want, as expected, without game.dead is true, then there's a problem with your a

basically waits for a touch and sets a boolean attribute to true. Using displaytext on another actor ive found that this boolean never even gets set to true after the press whereas on PC it works fin

If you increased the friction your character should stay on the platform. No need to constrain it to it.

There's a destroy behaviour in the actor that's spawned? If that's the case, and it fires straight away, without any attribute conditions, it'll destroy itself the moment it's spawned.

• the attribute game.dead is not being set to true, so its not triggering the spawn,