Change attribute self.motion.linear velocity X to 0

Constrain the blue box image to an invisible 250 x 110 pixel actor, use the invisible 250 x 110 pixel actor as the object 'your character'* collides with.

Then in the actual actor that is being spawned make a 'real' attribute, call it whatever you like, but POS Y might be useful.

The camera's origin is the bottom left hand corner of your scene . . . so rather than constraining the camera origin to the player's X and Y position you would need to (assuming you want the player to

To add to what @The_Gamesalad_Guru said, it sounds like the person making the tutorial created a game attribute called Random, and that's where the random function is storing the number it generates.

I'm trying to save the highest score in a game using the save attribute but I cannot seem to make it work. Any advice?

Change Attribute

up, but whenever i click success the Boolean attribute won't seem to change to true, and won't unlock all of the characters. I have it set as a non-consumable, and even if i have the success button c

(Quote)

constrain width to 5cos(self.rotation2) + 50?

up, but whenever i click success the Boolean attribute won't seem to change to true, and won't unlock all of the characters. I have it set as a non-consumable, and even if i have the success button c

constrain width to 7.5*cos(self.rotation*2) + 52.5

I'm not sure it makes sense (is logical) for a circle to rotate whilst constraining its width and height to a non-uniform ratio and not have it go outside those limits (60/45), as it turns it will nec

Make a self-attribute called "self.Taps" or something. You'll use it to distinguish each version of the actor from the others.

I understand I can create different shape of actors and constrain it to my characters X and Y position. But that is very time consuming and also has limitations. (depending on how detailed your chara

(The following is based on the assumption your possible colours are actually shown as images, rather than made with RGB colour attributes) Also not far off what @AlkaPP suggested.

Still having trouble, doesnt want to recognise the changing image attribute.

@jigglybean‌ Can you tell what you exactly mean? Where should I constrain to the table?

The issue here is that you can't use the actors self.position.x in an interpolate. That's why it is going super super fast. What you need to do is to create a new attribute (real) inside the actor and

Is there a math way to constrain the size of the actor based on it's rotation?