In your block actor, you'll need an attribute that changes value when the block is placed or has come to a stop. You might decide this by velocity=0 or touch is released or some other method. You'll

Change Attribute self.randomChoice to random(1,4)

@Lucamc If you mouse over the attribute name or click on the ellipsis (...), you should see the full attribute name. For expressions, clicking on the 'e' will do the same.

Also, When I've spawned the actor I want to constrain the rotation of the actor so that it essentially points towards the center of the screen - is this possible?

You can use the "Change Velocity" or "Change Attribute" behaviors, for instance:

Also, if collisions are important, then you would probably have to use a separate hitbox. Or make rules for image, width, height, position offset for every single frame, but that is not fun... Trust m

ATTRIBUTE DESTROY ACTOR

Change attribute game.StartTime to game.Time

If the projectile is moving up from the bottom of the screen, constrain the width and height of the actor to a value relative to its y position. On a 320 height scene, you would use something like co

And custom collisions!

@BrassMonkeysUK Yes, you constrain self.Rotation to that whole expression.

If attribute self.Graphics.Flip Horizontally is true

It sounds like everything in the first section of your rules (that determine normal movement) needs to go inside of a rule with the condition When attribute game.moveToClick is false.

No, don't embed the rule if you want it always to trigger. Just do If attribute self.Graphics.Flip Horizontally is true then [rule for shooting to the left].

I haven't watched that video but the general idea is that accelerometer values are neutral at 0 and then small tilt motions cause the attributes to become either positive or negative depending on the

Are you using different images for left and right facing or are you changing the actor's flip horizontal attribute? You can set a rule condition for either of these methods (e.g. If self.Image=left.p

One more question... I did exactly what you said. I double clicked on my character and added an attribute that I wanted it to do. However, I deleted all the other attributes because it was in protot

Yes, that's correct. It's entirely possible to create an attribute that only certain instances use or that each instance has a different value for, such as self.Health or self.Speed.

So if I create some attribute for a character in a specific scene. Let's say it was under the prototype. If I use the same character but want it to do something different in a different scene I shou

When (all) conditions are valid: Actor Collides or overlaps with actor of type hero Attribute self.Color.Alpha ≠ 0 Game Over