tried that doesn't work, let me try simplify would it be possible to constrain the touch position to a certain Width + height ?

Interpolate attribute game.Audio.Music Volume to 0 Duration 3

I am trying to spawn a grid of cells with multiple spawners and each cell needs to store its own row and column number in self attributes when it is spawned. I am trying to achieve this by using the X

Constrain self position y to devices/touch y

What rule condition are you using to constrain the actor to the mouse position?

If that condition is a attribute that changes to "True" it will stay "True" until you set it back to "False" a reset scene will not set attributes

Change Attribute game.LayerNumber = 1

Change Attribute game.LayerNumber = 1

Here's a version where you can set a game attribute for any row you want. I tried it with row 1 with the same large table and it was just as fast, maybe faster.

so i have a pause button and an actor follows my finger in the Y direction but when i press pause it moves the actor to that position how do i disable touch area on the pause button so my actor won'…

This is not an intuitive aspect of using GameSalad Creator. Only unlocked actors can access scene attributes. So if you want to change (e.g. Change Attribute) or use (e.g. in a rule condition or a m

its original one. The enemy image is not a game attribute, so why wouldn't it reset?

I heard interpolate may be better in terms of movement but won;t work with collisions. Is that true?

is there a self.attribute that will let me "control" the layer that the actor is in ?

I've had troubles when I've removed attributes and not removed all expressions using that attribute. Deleted any attributes?

Yes move to is tricky business sometimes. It definitely takes finesse to use. You could also constrain the velocity of the enemy to the main actor. I'm not at my computer but I'll post the expression.

If the condition is a game level attribute you need to manually reset it. Scene reset only affects scene level stuff.

I've heard Move To can be buggy. Another method is to constrain an angle attribute (e.g. game.enemyDirection) to vectorToAngle(enemyX-playerX,enemyY-playerY) and then have a Move behavior with game.e

If you want to save attributes, you'll have have to use the Save Attribute behavior.

anything you store in an attribute can also be saved, but requires more rules