Ok ? What are you saying here ? That constraining a value to something results in that value being constrained to the thing you are constraining it to !? (Image)

(Quote)

and two constraints which are turned off. The constrain forces position x and position to be rounded values all the time to simulate the fact that they're integers.

Then when every percent is greater than previous percent...change attribute progress bar to progress bar position +2.7px....

try it yourself make an actor with an integer attribute (let's call the attribute 'A' and give it a value of 10), now interpolate A from 10 to some other value like 20 . . . then display 'A' using a

I'm not a fan of the endless decimals either, so if I need to, I just constrain my actors' co-ordinates to their floor values.

(Quote)

All time attributes run automatically, no matter what rules you put up. But something to keep in mind is that an actor's time attribute resets to 0 every time you enter a scene (by changing or resetti

Yes, I'm purposely using change attribute instead of move to to get that jumpy look (don't have to make animation sprite.. lol). But like you said, it might be better if it have smoother movement. Tha

by some other factor, for example if you make an attribute called 'speed' and set that value at 100, then use game.time * game.speed as the angle that cos and sin operate on then it is 100 times fast

Actor has 6 real self attributes and 1 angle attribute :

Two game attributes: firstPosition, secondPosition

So if you're using game.score to determine the width of the progress bar and you have a maximum score of 500, you would constrain self.size.Width to (game.score/500)*270.

I have a progress bar that is 270 pixels wide. I have made my variable equal self.size.width(of the progress bar). then constrain self.position.x = 27+(self.size.width)/2. So the problem is that I can

Make an actor with an integer attribute, let's call it AAA.

Not at all ! It works with everything except for the storing of values (so writing a value into an attribute or table).

@Socks Ohhhh ! now I get what you mean ! but that only works in a display text man , but if you were to put an integer value in a change attribute that would be different , this is why I was saying c

Because a real attribute can store a non-interger value.

@Socks then why is the result different when I put a real attribute ? (Image)

Change attribute stores a number.