1. Created an attribute on the NPC character (npcangle), and constrained that to vectorToAngle(game.Player's x-self.positionx, game.Player's y-self.positiony).

if attribute score >or = 100 cange attribute newunlockattribute to 1

thanks, i did add a change attribute to 1030 which the actor is already at that position, and didnt work but is working now with the timer you say, thanks very much, i just dont understand why the ac

Use a Change Attribute behavior to move the actor to where you want it to be. Then drag the interpolate behavior under it; as GameSalad reads behaviors from top to bottom, it should load your Change A

In that case, yes, he would have to constrain the Table Cell Value to an Attribute, then use that.

Change Attribute self.unlocked to tableCellValue(tableName, row, column)

Constrain seems to have done the trick

Yeah, use the Change Attribute behavior to change self.colors, and Change Table Value to change the false character to 'true'.

that is called character unlocked with a boolean attribute... on the rows i have all the characters that are able to become unlocked and they are false... NOW here is the part that im not getting...

Actually, if I had to guess I would guess there's another condition (i.e. attribute) in your rule that isn't getting reset.

You can adjust positions in small increments (pixels) with the arrow keys once an actor has been selected on the scene. You can also type in self.Position.X and self.PositionY values in the attribute

That works, but because some of my code has been turned off I did not want to have to sort though it to find every instance of an attribute.

If you mean checking to see where your attribute is used, select that attribute and hit delete. If it is being used, it will inform you which actor is using it. If it isn't being used, it will delete

@Nklrcade There are definitely ways to find out when this is happening. Besides DisplayText, which is helpful but is a constrained attribute, you can use Log Debugging Statements at various points in

So perhaps a bit more info might help: what are you using game.Moves for? And does this attribute's value start out as 17? And what else is happening in the Rule when you use the equation?

Hi @KeithQ Make an integer game or scene attribute, let's call it Order, set to 1.

Instead of doing a change attribute do a constrain for the Y origin.

Great! Many thanks, that slowed my character down to a stop which was exactly what I wanted. I did so by making a speed attribute in the Game section and added the speed attribute for each direction.

Here is a version of @RThurman s demo without timers and less Attributes but with a constrain behaviour. (I added the constrain behaviour in the actor and turned the timer off).

The result 89.47 is when self.Moves = 19, so the attribute must be picking up an extra 2 from somewhere, sometime....