need a game attribute for each block's hitforce (constrained to that magnitude formula above) or else unlock each block and add that rule for EACH bad guy.

constrain attribute:

If you have it rotate in intervals like 0,45,90,135.... then you can just have an attribute: randomdirection.

Maybe every second, check to see if it's shaking. If it is, add +1 to an attribute. When it reaches 60 or 600, depending on the amount of time, unlock the levels.

ability to set if shake for (x) time then change attribute.

You could use constrain and the self.image attribute.

You could use constrain and the self.image attribute.

Anyone know of a way to set up so that If the player shakes their iPhone for a gratuitously long period of time (like, 10 minutes) the game triggers a change attribute behavior?

I'm wondering if anyone had an idea if there was a workaround for that. For example with a math constraint that would put the objects in the right place relative to my camera size or just a general id

In the first half of my response I was trying to throw out an idea for how to make hit points based on collisions with the ball AND with other blocks. That's where things getting really tricky (and re

I used a combination of the Y < 50 and NextGen's idea. Y < 50 stops the button press from moving the character and once the inventory is open I have the attribute true and he won't move

Change attribute game.inventoryactive to 1

create an attribute for when HUD is pressed. When the HUD is pressed change attribute to true, otherwise false.

Or just don't worry at all about blocks hitting other blocks (as fas as damage is concerned). Then you could constrain game.BallsVelocity (real) to magnitude(linear.motion.X,linear.motion.Y). This wil

block's attributes or otherwise you'll need constrains. Basically you want to know how fast the ball is moving when it collides as well as how hard the other blocks are traveling when they collide. T

I've tried constrain the block to the x position of the platform and it still shows no linear velocity.

You could constrain their position relative to the previous actor... based on rotation and cos/sin... but wow... that could be pretty laggy and tedious to set up.

It has a velocity in the expression so I would assume that would be the number to start with. try adding a change attribute that sets a specific x and y velocity.

Well you could have a game attribute that is constrained to Abs(Sqrt((self.motion.linearvelocity.x*self.motion.linearvelocity.x)+(self.motion.linearvelocity.y*self.motion.linearvelocity.y)))

***EDIT*** I'm going to try to make my description simpler. I have an actor whose logic says, if attribute = 1, then change attribute to 2, if attribute = 2, then change attribute to 3. Should I ex