I'm experiencing a problem with collisions when dragging an actor around; the actor will stutter through the walls or just move through them.

I literally have no clue what rules and behaviours you are using, how they are set up, how they are triggered (and so on) . . . . threads move immeasurably faster when someone is willing to reveal the

--Constrain Linear velocity X to 5*(Mouse.X -self.X)

Change attribute game.switchdirections to 1

          change attribute game.firstTouched to self.myColor

The point is that interpolation takes the actor out of the physics engine temporarily, so it simply doesn't detect collisions. The actors not being interpolated should potentially still detect the col

When interpolating, collisions generally don't work. Use Move To instead.

change attribute "randomTime" to "random(2, 10)"

Self (Actor) Attribute:

i using attribute

Make an attribute or table to save the information. Load!

Is it possible to change the initially loaded screen based on a game state(table or saved attribute) - without having another scene to determine the first loaded scene - ?

* When touch is pressed, change attribute: self.number to random (1,20).

Like @The_Gamesalad_Guru says, you can use the touches.count attribute.

In the expression editor (the 'e' on the right of the text field), simply choose your "coin count" attribute from the list.

I have searched the forums and tutorials and haven't found a good answer. How do you simply display a number based on an attribute that you start with? Say you want to start with 50 coins. I set up an

It uses GameSalad collisions to calculate Pi via the Monte Carlo method. Anyone else got any Pi related projects? If you throw in an Arcade or App Store link, I'll tweet it out!

I am trying the solution with callback attribute of IAP purchase request mentioned in another thread.

just typing the value into the Angular velocity attribute field saves you a behaviour . . . so not really much in it.

(Quote)