(Quote)

But by using magnitude , I will create a self.distance attribute and constrain it to magnitude(self.positionx - game.playerx , self.positiony - game.playery)

I think you are conflating a bunch of unrelated things here, Constrain, Magnitude, Rules, Display Text, they all have separate and unrelated functions . . . .

You use the constrain behavior to constantly update the value outputted by the magnitude function. You want to do this so you can always evaluate the distance between two things. If you only evaluate

its the same as constraining magnitude to calculate the distance between player and an enemy and then adding a rule to display text. why constrain instead of using a simple rule, does it work differen

Here's why. You can do Numeric Expressions in GS now, so you can directly enter the Mod1 Attribute on the left side of the equation (you couldn't do this in the past). Also on the right side of the eq

@freneticz, Gamesalad has changed since this piece was originally written. You don't really need to assign an Attribute as Mod1 now because you can have create Rules as a Numeric Expression now with m

(Quote)

OK -- use the following equation in the constrain rotation behavior:

create a game angle attribute: Angle

-create game attribute GridSize

You can "pass" an attribute value from one actor to another using this method:

Hello is there a way to do this :

It's the swinging around and controlling the rotation that has me a little stuck. One version I tried was to simply constrain the triangle's rotation to vectortoangle(game.accelerometer.x,game.accelor

@tatiang is correct about 1, but you can fake it to an extent. Having an actor copy its text into a buffer and then pasting it into another "notebook" table or attribute would be pos

@RocketBrain The %360 is the mod() function which returns the remainder of a division problem. It can also be written mod(self.rotation,360). So if you had values larger than 360, it would constrain

Setting it up like that will likely cause you issues (rotation and V2A work on different value ranges), also there's no real need to introduce another attribute ('MyAngle'), it doesn't seem to serve a

I was going to make an attribute Max HP and then use this formula

that loop condition maybe the issue. I see you resetting the rule but not the loop condition. That condition makes no sense and the random should be picked and stored in a self attribute so you can ch

One thing I noticed is that in your Note actor, you have a Timer set to every random(0.5,1) seconds with two rules inside. Those rules will trigger whenever they are true even without a timer. So th