You can wrap the animate behavior in a rule for When actor collides or overlaps with actor wall --> [do nothing]; Otherwise --> Animate. Or, you can add a boolean attribute, self.stoppe

then when you hit enter, add all the "letter" table values, and populate a text attribute with the result of all the letters added together.

To my knowledge there's no way to delete a character from a text attribute.

no, change attribute so it happens instantly. you want to change the value of the x position

If conidtion valid. - attribute-self.motion.linear.velocity.y >-20

sometimes (really sometimes after few side wall collisions), it starts going in the opposite direction. Meaning lets say it hits right wall and bounces to left wall. it some times comes back down ins

When your event happens, call a boolean attribute to be TRUE, call it something along the lines of 'gameScreenFlash_Red'. When this event calls, change your sprite to have an alpha value of 1 (or, if

Attribute: game.gametime < 90

You would want to use a GameAttribute in place of the row setting in both displays. Then Set that game attribute randomly.

All of GS is pretty much obvious. It's just logic and the computer does what you tell it when based on attribute conditions. Learn to look past the GUI and think in logic a to b to c to d.

Here is what you do. Add rule inside that rule. When attribute self.position x = (position you want)

Rule: When touch is released, and an attribute I call game.Page5ChipRight is False :

That would still require a extra attribute though for each achivement, when you can just make the achivements boolean attributes themselves.

What did you try this with. Change Attribute, Interpolate Attribute, Constrain Attribute, Etc…. ?

Attribute: game.gametime < 90

you really want to replace the x with a selected attribute for numberValue … or a number

This screenshot should help show you where you need to be to create a game level attribute in the Windows Creator.

2) Make two new attributes

gameAttribute: need2destroy … index type

that store static data unlike a game level attribute that the processor has to check ever cycle. By using tables we avoid lagging the processor. So you address a table row or colum just like you woul