I have an index attribute that is randomly assigned to produce a number between 1-90 when the "next card" actor is pressed. When that attribute produces a number, my actor "

attribute --> game.screen.size.width=1080

COLLISIONS

COLLISIONS

I know with change attribute behaviours, they will activate in order within the same code cycle. I did over 200 behaviours each changing an attribute to +1, and the results were instant. I know there

Once you now what value is being returned, you can go from there. Make sure the attribute type is also the same. If it is a text now, and a numeric before, then that might be a problem.

In my app I have an attribute called "TableRunner" this attribute is running on the table with loop until it finding the correct date, then it changing some attribute to the value of

Needs to be game wide attribute.

I am currently setting up Gamesalad with in app purchases and I have seen that you need a callback attribute. Do you have to make this or just type self.callback in the box and it will do it on its ow

You can constrain the actor's Angular Motion to a positive value to rotate Anti-clockwise, and a negative number to rotate clockwise.

The "When Touch is Pressed" rule condition is only true in the moment that the actor is clicked/tapped. So if you have something quick like a Change Attribute behavior, it will alwa

You can use the Device>Touch.Count attribute.

or you can constrain real game attribute to y position of the player and have a rule on the platform

I have the jump-through-platform formula going; the thing is, when my actor makes ANY sort of contact with the platform (mid air, lets say), it effects an attribute that I ONLY want to be effected whe

@ADSentertainment

To work around this, use one loop, and increment the row and column attributes inside it.

My left and right movements are with accelerator behavior in a rule, and at the bottom where it says "otherwise," I change attribute: velocityX to 0... (in other words, when I stop p

Hey everyone! I just recently downloaded PhysicsEditor to create custom collisions and I am having difficulty getting the file to work with the software.

I found the problem. I had an interplode behaviour below the constrain changing the self.positionx in order to ignore gravity. This caused the constrain to only check for the position before the inter

You want to learn the save attribute behavior.