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...

Unless you are changing the attribute types, you can simply rename the attributes and the changes will be applied globally.

Didn't they change the way constrain's work? I thought they change Constrains (in .80 patch) so they don't work on offsets anymore. I could be wrong though.

lastangle is just constrained after i've constrained diffangle.

you can still test for collisions without "Collide" behaviour, but the actors will just pass through each other.

Thanks very much for posting that, I had done it with just one constrain so there was a nasty jump on touching, concise and to the point, but butt ugly (Image)

maybe a rule thats states if the ball overlaps or collides with the target then change a game attribute (game.HitTarget) to 1 otherwise have the attribute change to 0. Then create a rule on the ball t

Make game ? attribute

create two attributes, call them like collideX and collideY

You did it the right way. To use rules in the ball, you would need to have a game attribute, like your "collidable" one in the peg, for every peg...the pegs would update their respec

i was just playing around with the Pachinko example and I wanted to make the pegs not collidable if i click on them.. the only way I can see to do this is move the bounce/play sound rule into the peg

Do you have rules that states 'when touch pressed change to true' otherwise 'change attribute to false'?

what about the opposite? Constrain an invisible actor under the player.

when a barrel is spawned also span an invisible actor and constrain it's X to the barrel's X and constrain it's Y to the barrel's Y + (barrel height/2)

Constrain Attributes

In GS, you COULD use collisions, but then you'd have let's say 100 (10x10 grid) actors all testing for collisions.

if actor collides with actor of type alien, add 1 to actor "touchcount" attribute

Definitely a valid solution that countless chefs have used, but it would be nice to use gravity... and yet not use it in some cases. I would certainly like a boolean actor attribute in a future releas

Change attribute: game.levelTime to game.levelTime+1