I created a utility app. I have a timer that counts down from 60 minutes. I made a integer attribute called mtimer that is set to 60. I then made an actor with a rule that displays mtimer-1. Works gre

just instead of having change attribute: self.change.Color to (self.change.color+1)%3

change attribute EquippedWeapon to (EquippedWeapon+1)%6

I have 1 actor that displays different weapons. It shows one weapon at a time. When pressed it is supposed to switch to the next weapon (image wise) and change the Equipped Weapon attribute up 1. When

Constrain Attribute

I found an error and solved the problem. The error was that I was saving an attribute at the same time when it was interpolating: I put the save attribute inside a timer with "after"

You will need to use save and load attribute

Nevermind I seemed to have worked it out so would you have a sceneX and sceneY real attribute for every scene I want it to remember where I left?

You would need some game real attributes lets call them Scene1X and Scene1Y.

the cloud to go from right to left: put change attribute self.motion.x to -1*100. Then you have to add a rule that check:

For spacing just use 1 pixel and then Constrain the replicate number to your heath number. so a heath of 100 would appear as 100 pixels wide and will grow and shrink as the value you are constrained t

constrain self.size.width to 100*game.PlayersHp/PlayersHp

Change Attribute self.motion.Linear Velocity.X to 50*(cos((((vectortoangle(self.positionX-OtherObjectX, self.positionY-OtherObjectY))+90)*2)-(vectortoangle((self.motion.Linear Velocity.X/50), (self.mo

With "all your load attributes should be right when the game starts" do you mean that it is not possible to have a load attribute later in the game?

I apologize if this topic has been already discussed, but I tried to search for "save load attribute" and the likes and the results are not as expected (maybe there are problems with

mu-kowAAPS I can't do a simply constrain because the speed (as explained above). Perhaps with this image you will understand what I mean:

Here is what I did. I created a new game and made three game attributes (all real), angleOfTrajectory, distanceFrom, and Power

for the 100s place when attribute score is greater then or equal to 100 change alpha to 1 and so on.

I can't remember if the cam origin is available as a game attribute, but if it isn't, just make an unlocked actor in your scene and a new attribute called cam.origin.x and constrain that to the scene

Why can't you just constrain the shadow to the ball with a small offset. (ball.x-2) (ball.y-2)