Either just pin the one you want, or if they are grouped (animation frames), you'd have each group pinned and you only change the current frame to show the appropriate piece of armour. Depends how you do things.
The Pin behaviour is the simplest.
int(Random (1,101))
Develop games in your browser. Powerful, performant & highly capable.
expressions
You can use Choose, or Random (converted to an Int).
This pops up now and then. There are some recovery instructions here:
recover
You'll need that Canvas plugin:
GradientBasedScaling.capx
Canvas
You can only test for the collision in the first place if you know what to test against, so the point is moot. If you want to abstract the object, you would use Families.
bees_BHT_b.capx
The bees get stuck on the rocks, so you'll need to come up with a better way to deal with that.
philx
Timer is now a native C2 behaviour.
Not perfect, but closer:
bees_BHT.capx
Ah, I did misunderstand what you were doing. Colludium is correct. If you destroy the object, you can't then get properties from it. Either do what AllanR suggested, or Colludium, or store the values prior to destroying.
Member since 28 May, 2012