@applucinate Then you can use Interpolate instead of Change Attribute to make it scroll.

I've always done it by saving the letters inside a Table instead of a single Attribute. You only need one counter to tell you which Cell to add to next, as well as which Cell to delete when a backspac

You would need to create an "real" attribute. Eg .Call it Actor_Y_Location.

Even though the display test changes correctly the attribute cannot be shut off once the app is running.

Make a global boolean attribute. When a new actor is placed, change it to true from within the new actor. Have a self timer that gives it a second of immunity or similar then say 'if (that global bool

You could use a constrain... but that isn't very good for optimisation. Oh, you could set a boolean that says it's movable or not, and then not use collide at all - instead use 'change attribute' to a

So... I used the change attribute to change my actor between movable and not movable. I used the display text function, to even show that the actor registered that it wasn't movable, but when another

So now I'm trying to implement a more custom collider around my hero. I figured I'd make a smaller box, constrain it to the hero, and switch any collision rules from the hero, to the box. I followed

I have a game attribute (boolean) called 'destroy letters' which is true/activated when each letter in the word is also checked (also booleans) and the user hits 'enter/return'.

So if the attribute heroattack (interger) = 1

And to anyone having the same issue as me, all you have to do is to create 2 Game Boolean attributes (Name 1 DefaultPosition and the other 1 GameOver). Then after you go inside your reset or restart b

If the character was a still image I could use a table and change its self.image using a change attribute rule and the characters shirt color would change . That's is also real simple.

(Quote)

whats wrong with using the reset scene attribute?

I wanted to avoid the issue with a lengthy "press" increasing the attribute until the person let go...but changing it to PRESSED solved the issue

The solution from @KevinCross should work just fine... anyhow, maybe try a slightly different way: change the attribute back, i.e remake the PlayersTurn attribute to a boolean, and make sure you have

--Change Attribute self.motion.linear velocity.X To 0

Have a game attribute called Players Turn and set it as 1 by default.

I tried to put a boolean attribute

3 - change attribute (self.motion.linear.velocity.X)