You can search a text attribute to see if it 'contains' a character (or string of characters). Example:

Hi tatiang, Unfortunately I did review all of that before my post and could not find anything wrong. I ended up removing the attribute to decrease the game.3lives and all of a sudden it started counti

Will try it this morning mate and update this post. The difficulty at the moment is for GS to consistently detect collisions for multiple spawns on the same actor.

• Built-in attribute to specify when keyboard input has completed

Then have a single behavior: Change Attribute self.Letter to tableCellValue(AlphabetTable,self.randomNumber,1). If you have images named A.png, B.png, etc., then you have one more behavior after that

Do you have more than one actor or more than one instance of this actor on the scene? Did you select game.3 lives from the expression editor drop-down attribute menu or did you type in game.3 lives?

Constrain attribute

Can you not have an enemy have a self attribute that assigns it a value? Thus saying if mario hits enemy, AND if enemy is value x then do y? Thereby allowing one enemy actor but having an assignment o

This is weird!! Attached is some 'code' I have for reducing a 'game3lives' integer attribute. Unfortunately when one of the conditions is satisfied, the count is decreased by two, not one. I confirme

I have a character in scene, when i touch it load the keyboard display behavior, simply to change an attribute (Or do anything doesnt matter). It opens a box to write then open the native keyboard of

(Quote)

It will take a long time to spawn 1,000 actors, but all you need to do would be to have a position attribute that increments with each new spawn.

Using my example above, you could also say IF mario hits enemy and boolean is true (the boolean trigger we used for the hit box to know to constrain to enemy) THEN destroy enemy and move hit box to ne

Have an invisible actor that will serve as the hit box actor. Use this actor and constrain it to your enemy's head or whatever. Now i know this becomes hard and bad on performance when theres 20 enemi

Constrain top enemy to self.head.

Problem is, the enemy actor spawns multiple times on the same level and therefore I would need to create 20-50 iterations of the same actor and 20-50 attributes to track them (not something I want to

Change attribute self.color.alpha to 1.

(Quote)

You need to return the values you interpolated back to their original settings if you want the same interpolation to run again, you can interpolate them back or simply change attribute.

(Quote)