Yep, you never want to constrain or interpolate an attribute to itself. When I need to do something like that, I usually have Change Attribute self.originalWidth to self.size.Width at the top of the

So basically I want to constrain the actors width and height to the actors Y position so that when the actor moves up on the screen the actor gets smaller. This is what I have. The problem is, it does

You could constrain one actors Self.X and Self.Y to the others actors self X and Y.

Constrain Attribute self.Position.X to game.Touches.Touch 1.X

I checked out your simple test project. I see what you mean. The line appears while the camera is interpolating from one position to another (using the scene.Camera.Origin.X attribute).

You can try and use a multiplier with game.Display Size.Width, along-with a page(screen) number attribute.

To add: whatever the cause of the lag, the possibility that it's caused by using a global attribute instead of a scene or self attribute is practically nil.

Yes remember that when computers execute code it virtually happens a light speed as it's flowing electrons. So when you touch both can happen before you release your finger. By using release you tell

1. You can try unlocking the upper block and constraining its self.position.X to the lower blocks self.position.X. That will alleviate the need for "global" game attributes.

Have an integer attribute let's say collectedeggs

Integers can be substituted for index attributes.

So then I look into the actor to see what's wrong. Then GameSalad tells me my Change Attribute behaviors were 'null'.

version is still missing the "create attribute as index" option.

Change attribute tick.position.x to -100

I have an integer attribute game.mute. When it is 0, the game is not muted. When it is 1, the came is muted.

It might be a bit of a hack but couldn't you just make your own global attribute and set it true if you are going to export as Android and false if you are going to export as iOS. Using this attribute

Hi Richard, yes, as @sparkania confirmed, you can make an attribute specifically for any one actor; in GSC, these are called self attributes.

can I assume you are wanting a single actor to be Spawned and use an attribute (integer) which you are not seeing when programming the Prototype?

I have 3 attributes

You would need to make a boolean attribute, and call it something like "grounded" and have it set to true when the character is in contact with the ground, and false when it is not.