thats why. So i did another test, made my own attribute, had a timer every 1 second change attribute to attribute +1 and put a button to pause the game that also displayed that attribute i was adding

You maths elites, keeping all the good stuff for yourselves while we, the masses, fight amongst ourselves over a 'constrain to X' behaviour and 'change image size'.

Wondering if anyone knows a way to control the restitution of an actor based on how fast something collides with it. Or an entirely better way to handle collisions to make it seem more realistic.

Why not just get rid of the 'spawning' behaviour and use a single background image moving from right to left - with the scene attribute 'Wrap X' switch on ?

When the object is touched > constrain it's Y (vertical) position to the mouse (or finger) Y position > when you release your mouse/finger (the 'otherwise' part of the rule) then interpo

when you restart the level just change attribute score to 0.

I have a little problem with my backgrounds scrolling in my iPad game. The iPad version of my game will only spawn a new background actor (that is constantly moving left) once the first background act

so all you would do then is change the attribute back to 0 when you press the retry or replay button

would that attribute be a game attribute or a scene attribute?

The thing is in my game i have an attribute that is 0 and when it is 0 the background moves, and when you hit an obstacle that attribute is turned to 1 so it stop the movement of the background and th

It is most likely the acceleration behavior on the Hero that is causing the problem. Acceleration is a persistent behavior (much like a constrain behavior), and will 'push through' a rope actor.

what i do is create a game boolen attribute called groundtouch. now when actor collides with ground change that attribute to true, i believe you have arrows to move the actor so add a new requirement

Red arrow: when touched changes attribute X from A to B.

The move behavior is causing the problem. Try change velocity or try a change attribute behavior and change the self.linear.motion.velocity.X

Referring to your 2nd question, if you want an actor to flow an other one up and down, it may work if you constrain the attribute!

The X position will then change to a position very close to itself very quickly. The change of the X attribute will be so subtle and fast it will seem as if it is vibrating, shivering or shaking. Doin

Thanks for the explanation. I'm using text plus the value of an attribute

so that's fine if you're only displaying text, but if you want to display text + the value of an attribute?

Anchor and Vertical Anchors (via change attribute) to various values - and then used a rotate behaviour - but the actor just rotates around it's centre, I was expecting (hoping) to see it's centre of

In the rule that restarts the level change the health bar back to it's original size with a change attribute.