You might want to constrain the rotation of the character though because i bumped into something, not sure what is was, but it left me spinning and i couldn't do anything about it (Image)

inside the spawned actor create a "change attribute" behavior that will set self.green/blue/red to random(0,1)

My overall goal here is to detect a certain specific combination of events, which are tracked by one game attribute (the binary string). For example, 5 actors would each affect one of the placeholders

In your original questions, you asked whether there was an alternative to using gravity and collisions. This is one alternative but it might not be the best solution.

every [ 2*game.attributeX ]

Also note the performance is probably really bad because the constrain function is running all the time (Really it should probably set a timer to stop it running after the interpolation)

up to 100 nothing I change in the setting or my attribute seems to change this - is it the floor( self.Position.X - self.leftLimit )/( self.rightLimit - self.leftLimit ) formula?

Yes I know. You have attributes together that shouldn't be together. You have the destroy attribute in the same rule box and it destroys the fireball before doing (or finishing) anything else you want

i tried to move that rule into a different actor that i could possibly reuse in other projects.. stopped working altogether.. i just got a blank screen. any idea why this would happen? also you can't

EDIT: also, the camera cannot go past the boundaries of the scene. You tracker actor can, so you just need to use min and max on the constrain...

Like you said, having 80 objects with physics, collisions, etc. is very taxing on the processor.

Hello. I am making a game with blocks that stack up using gravity and collisions. There are 8 columns and 10 rows which these blocks stack up in. I am noticing a good amount of lag. My objects (bl

You need to separate 'destroy' from everything else and make sure it fires after your other rules. Otherwise it goes off first and your other attributes don't have time to fire. To do this just make a

maybe set a game attribute like

Three words: Constrain is bad!

it can be found in the expression editor. You need to constrain the ball positions to global attributes.

particularly from a collision, it'd be great to be able to access/alter the other actor's information. I believe Box2D 2.1 provides easier access to this information on collisions?

"Change Scene goto Scene(game attribute random_number)"?

game attribute random_number (integer)

As you scroll the background, the camera is moved through the scene. To keep the ball in the picture I constrain its X position...