@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?

and moving downward animation). i need an attribute that also allows the speed to be adjusted I dont want my enemy actor to move at a fixed speed. I'm willing to pay i hope someone is up to the task

Constrain self.position.Y to (whatever).

I dont know if you still need to constrain your attribute to the table.

* Change attribute --> self.LasersToSpawn = random(1,3)

(Quote)

* The starting height of the Y position, as found in the self attribute.

Create a global integer attribute, let's say Color and have your main actor (the simon says actor) carry the timer every X seconds change Color attribute to random 1-5. For each number 1-5, create a c

* Make your own game.timer. Simple have a game.attribute called Time. Have an actor on screen we the rule:

I have managed to find a number of tutorials on how to set up an hours:minutes:seconds:milliseconds timer. My problem is that because it is linked to game time, if you look at the menu for 10 seconds

I want to be able to throw a ball every x seconds. Ideally, I would like the time intervals to be a random time between 1 sec to 5 sec. How can I do that?

The problem is that you typed a mathematical function (random) into the text/number field of the Change Attribute behavior. You have to use the expression editor (the little 'e' symbol) to enter func

since putting up Change Velocity will screwing up the movement to Y direction, I created enemySpeed Attribute integer attribute to determine what velocity the enemy1 should use.

Constrain attribute:

Make an index attribute.

if game.score > game.highscore change attribute game.highscore to game.score .

So the key can be anything I want, as long as I use the same key to load the attribute?

Normally you would constrain the camera coordinates to the player coordinates.