Change attribute: self.Motion.Linear Velocity.Y To:random(70,120)*(-1)^(random(1,2))

Here's a video from the attached file of what should happen when you use Load & Save Attribute behaviors but exit out of the Preview and return (on a Mac, not on a mobile device). When you ch

I just have like I said a game level attribute integer, default at zero, that when the score exceeds it it sets that to the high score, and saves the attribute to A. The main menu scene that the progr

Timer (every .4 seconds) Change Attribute: self.myRndNum To: (self.myRndNum+random(0,2))%4+1 Spawn Actor: Position^: 102+((self.myRndNum-1)*187) Position>: 0 Relativ

* Create a real or integer attribute and lets call it something like "interpolate_time"

So in my scene, if the player's score exceeds the high score, it sets the high score as the score. Pretty basic. Then it saves the highscore attribute as A. Then when the game boots on the main menu,

an interpolate behavior. I also use a game level attribute "game.state" for my main character. So if game.state = 3 then I have the interpolate coding fire and he starts to descend

Please break it down more simply. Furthermore do I need a new attribute for this?

Please break it down more simply. Furthermore do I need a new attribute for this?

Not sure that I understand you correctly...But couldn't you just record the speed (in a separate attribute) right before the power-up is used?

So I want to alter the game speed when my character uses a power up. I figured that out no problem. I have a game level integer attribute I am using for my game speed. As a side note, my game speed is

Here's a demo that stores enemy actor locations in a table and then moves the hero actor to the closest enemy. It's likely that to use this in an app, you'd need to constrain the table cells to the e

Keep in mind that depending on your game setup, you might have to constrain the table cells to the enemy positions by using a Timer. This can have a pretty negative effect on app performance.

If Touch is Pressed, Constrain attribute [ self.position.x ] to [ max(min(game.touches.Touch1.x, game.displaysize.width+self.size.width), -self.size.width) ] Constrain attribute [ self.

When [Magnitude(self.LinearVelocityX,self.LinearVelocityY)] < 140 Change Attribute: self.myDirection To: VectorToAngle(self.LinearVelocityX,self.LinearVelocityY) Change Attribute: self.Motion

That is a good idea but the only issue is knowing the direction it is traveling since it is always changing when it bounces off things. Basically I just want balls bouncing around the screen at a cons

DO - constrain attribute - self posiiton.x to game.touches.Touch 1.x

Have you tried setting the actor's self attribute under motion, max speed to x and then check apply max speed?

Change Attribute: self.Motion.LinearVelocityX To: 150*cos(Direction) Change Attribute: self.Motion.LinearVelocityY To: 150*sin(Direction)

Right, there's no way to make a rule condition for the submit button. I wish there was. So you either have to determine if it's not blank or if it doesn't equal the current value of the attribute in