I would make an actor attribute called something like start_falling_distance.

For collisions, it's a square shape, everything is, just like in GS. I have been trying to figure out how to fix that and I may have a solution, it just needs a tad more testing.

In the lines above, are you setting up a rule/attribute for each of these? If so how are you setting "self.positionOfPlayer" as one attribute? shouldn't you be finding both the X, an

on your main character constrain a global variable game.characterY to self.position.y

you really need to check collisions. it seems to be pretty off. im not sure how it works in corona exactly, but it seems like your png has a lot of alpha around your actual sprites. this would result

The reason your actor continues to spawn is because you never update game.numberThrown. To do this, put the following change attribute behavior after the spawn actor behavior in the rule you mentione

game attribute (integer 4)-numberThrown.

Also included camera constrain right and left scenes incase you want another option.

2 actors, with a collision rule that changed the value of an attribute, so I could view and debug.

how would you do that? again would you need to create a boolean attribute and an integer attribute? how does GS register/recognise a jump attribute for example? would you use an interpolate attribute

But why is it not working for me Gyroscope's way? Gyroscope, is it possible you can you upload a quick demo for me to download using the boolean and integer attributes you've explained above. I'll sen

What you did was try to constrain the individual rotations (around the centre) of your collision orb actors to touch. However, you already had the rotational change of proto ring smaller saved as Targ

I have added an integer attribute with the number of bullets I want to be the limit and set up a rule that minuses one each time a bullet is fired, but they still keep coming.....

whilst it's running, the collisions don't register.

as your Dog actor already contains all the attributes the computer can change during runtime...

I just tried something like this out and it seems that interpolate is still preventing a collision from happening. I have a bullet actor that grows in size over time (using interpolate). As long as in

The actor would need a constrain attribute:

None of the attributes are linked it or its width, so basically (as I see it) you are modifying an attribute that the game reads but has no way to display.

In actor1 constrain these attributes to self.positionX and Y

I placed the attribute (back to false) right after the "spawn actor" behavior (not in the actor to be thrown)