Do: Change attribute game.audio.sound volume to 0

Do you have "save table attribute" in a timer behavior?

I have a boolean attribute of Music. I have an actor in the scene with the rule, if Music=true, play music, change to false.

Constrain Attribute self.Rotation to vectorToAngle( self.Position.X - game.Mouse.Position.X , self.Position.Y - game.Mouse.Position.Y )+90

When attribute self.position.Y ≤ self.myMin, change attribute self.Motion.Linear Velocity.Y to self.mySpeed

(Quote)

Make two game attributes, let's call them PX and PY.

You cannot rely on the purchase table to be accurate, as it relies on an internet connection. When a purchase is completed the first time, save it to an attribute or a separate table.

Are you triggering the level unlocked based on a saved attribute, or based on the purchase table?

-change attribute game.CurrentLVL :to: 0

Change attribute game.Current\game.Unlocked :to: 0. Or do, when button touch is pressed :do: reset game.

Hi @Add some The most effective way to do this is to make all your attributes accessible from a Table.

It'd be good to get Play Sound supporting the use of Expressions to select the sound by name (as one can currently do to set the Image of an actor, using Change Attribute and an Expression to select t

google Socks link machine or Socks fast constrain. I think that'll get you what you want. If you just want one to sit on top of the other no matter what, just make two real attributes actorX and actor

If this logic is in an actor that is on the first scene to load, what's happening is probably that the actor is running the "Text attribute is not table cell" rule before the text at

Well i just want to constrain them together can you poin to a video that can help?

Input the keyboard text into a text attribute and then change the table cell to that text attribute. To know when the user is done typing, check to see if the value of the text attribute has changed.

I know this may be simple but how can i constrain two actors together? so when you touch it then it follows each other.

You can use a game level attribute to control the current action, eg. game.CurrentAction

Could you have it all in one table? Rows 1 to 100 for Dungeon 1, rows 101 to 200 for the next, etc. You could then change the row attribute (adding 100 depending on the dungeon).