I'm using rotate to position behavior and then constrain attribute to recalculate the position using sin and cos functions.

Using the interpolate attribute is not working as expected, because although the score attribute is declared as integer, when it interpolates it shows real values with two decimals.

When the stack is clicked, each card sends it's value (e.g. 1, 2, 3, etc.) to a global attribute. Then, the referee actor compares all the cards affected using max(x,y) to find the topmost one.

When you constrain it overrides the physics so it will not collide with blocks properly.

Those of you who have an Options screen in your game with on/off buttons for sound effects - do you use a constrain or just change attributes? Can't seem to get mine working properly...

constrain self.positionY to where ever you want the pong actor to be positioned

-- change attribute self.isTouched to true

I think you'll need to use constrain instead of change

i have a counter, that cout up +1 every time an event happens (it works, i can see it with display text), now i have another actor that has an attribute "self.temp counter" and a r

Create a Game Attribute called "Hero Y"

Create a boolean attribute self.OnTheGround

You just need to constrain the Linear.Velocity.Y to an integer value, so when the player is not in the air this value will be equal to 0.

Try this make attribute jump integer 0

Hi forum, I'm making a score counter, but I find the gamesalad text thing is pretty bad quality. I want to make my own numbers. How can i get my numbers to be the same number as my 'score' attribute l

change attribute, actor 2 position to actor 1 position.

Thanks for the reply Ginger! I did a heap more testing, and sure enough it kept doing the same thing. I still don't understand why it did, but my work around involved some attribute changing. So for a

1. Create a new game attribute and use that as the unlocking level cheevo, or whatever it's call. Create an new actor with the exact same rules as the one you have now. I know this sounds like it w

the way it knows menu selection is 6 is ive constrained attribute ytouch=floor(touch.y/32) i done this to create a grid layout for checking for x and y touch position that way if you touch anywhere be

My first game is nearing completion now, but I'm having a hiccup with the awards system. My game features 60 levels (10 levels per world) where awards are unlocked by completing each level within a se

just make some attribute,