of behaviours and rules in it when I deleted a attribute it froze for about 30 seconds trying to find things that were using that attribute. In this process the ram GS was using went from 570mb &

if attribute. level_select = 16

So, I'm kinda stuck. I'm making a multiplayer mode for my game, and i'm trying have multiple copies of the same actor on screen and i want each player to drag them and have the actor constrain the pos

What's interesting is that you can use constrain to move characters, but you can't use other options. I might be able to use math to trick my way out of this one.

Another trick that seems to improve frame rates is to set movement to false if an actor doesn't need it. This is where the problem comes in. Certain actors in my game don't need to move unless they're

I am having an issue with multi-touch! I have yet to find any guides or forum posts explaining it. I have multiple actors that you drag accross the screen using constrain behaviors. When I touch a ano

change attribute game.object to random(1,12)

if= click actor one= change attribute tag of actor 2 to 2 (this is the problem! more on this later)

I would simply store the last horizontal direction press in a separate Attribute, so that when he lands, you can "restore" the direction immediately afterwards.

First i have game attribute 'loop' (real) and 'number' (integer)

I believe, like rebump mentioned, that they may use "dirty (i.e. changed) attributes" to trigger non-timer enclosed rules/groups. You can set up a simple rule (with only one conditi

You only use real attribute if you need decimal points. That's the main difference.

code. I ask, as it would be funny to put a game attribute in that gets saved (like a high score) and have it track the number of times the app has run. Name it something else though. Then after li

Attribute: game.angleToPlayer

What type of attribute should it be?

With an Attribute.

My problem is, becuase I am using a constrain, when I don't "slide", I can just tap the screen, and the actor obviously just appears at the touch.

I have made a game attribute named "Menu active" (boolean)

And global is a scene attribute instead of a game attribute? Or something different?

Create two global game attributes, cameraX and cameraY