If you want the clock to move more smoothly, change the timer on the reset button to something like every 0.1 seconds and also make sure the change attribute within the timer is set to deduct 0.1 inst

Given attributes OriginalRatio of 1.5 and OriginalWidth of 480

I would constrain a separate image for the flash. It makes it easier to have separate images for different parts that aren't always going to be there. Atleast I think it does.

Other than that you can make an attribute or several attributes.

Perfect! Did a Constrain Attribute: self.Position.Y to: floor(self.Position.Y), which if I understand it right, should actually solve both issues, right?

And after 5 seconds they change an actor attribute to true.

@codewizard have you seen the self.attribute bug I posted? Will that get fixed in the next release - it's a major...

their size don't properly detect overlaps/collisions? I know that a bunch of people have asked about this in the past but it has never been fixed. This is a HUGE problem for me right now...in fact, i

(I quickly copied your set up, but I just entered 90° as the initial attribute value)

@Socks, the initial change attribute is simply because by default the value of that attribute is 0, which moves the actor to the right instead of up or down.

I don't think you need the initial change attribute (direction to 270°) it works fine without that ?

I noticed that if I put the random expression in the Direction field, the actor doesn't move but if I use a separate attribute it works. Try this:

Move, Change Attribute, Constrain Attribute or Interpolate would all work

I have read this basic but it more confused me on table attribute .

Attributes are simply variables from math or programming languages. They hold values. They can hold numbers (e.g. integer, index, real, angle), text (e.g. text), or can be true/false (e.g. boolean).

Capitalization of the second word is just a stylistic thing, you can call an attribute whatever you like ("Super fading magic thing" or "XBC491" or "SceneO

it's just a made up attribute could have been called getDark or LightTheRoom and you can pretty much create all you want. and I don't have the template but in this case the creator probably tied it to

do it). Regardless, the template has this change attribute command of Fade in/out. I kept wondering where this comes from until I realize that it was an attribute added by the template creator. It a

Is your Waypointcheck Attribute, Game Level? If you make it Actor Level instead it should be independent for each enemy.

The method @Braydon_SFX mentioned is a good way to do it. Another way is to make the fire animation a separate actor from the plank. You can then constrain the x,y coordinates of the fire animation ac