So constraining the attribute for the image boxes worked perfectly, but I also tried it for the buttons as you mentioned above and they no longer work.

constraining the attribute worked beautifully!

Use an attribute as the speed of the Move To behavior. Since attributes (aka variables) can change value, that will allow you to do this:

When you probably should be constraining self.Image to that expression value.

I made a Constrain Attribute called self.RedScore

change attribute

change attribute

I can see that the data is being copied as I have a display text attribute that shows up with the image, and it displays exactly what it should.

Constrain alpha to 1000*sin( self.Time *2000)

to do this for... I have made a game boolean attribute labeled invincible... And I have a index attribute labeled blinking... Now what lol I'm just trying to find the easiest way to do this and make

(Quote)

That was my assumption making the demo. But try taking @tatiang's, and removing the constrain from the red actor. Then move it manually into the path of the white actor. Collision fails to take place

So it is a "dynamic" hitbox. I've never seen GS properly detect collisions on a dynamic hitbox.

I will go back to the drawing board and try again with the Red Score attribute. I'll post back later with an update. As always, thanks for your input. Much appreciated!

As for the type of Red Score attribute, it shouldn't really matter but if there's ever a doubt about an attribute type, make it a game attribute.

Do you think my problem was where I named my Red Score attribute? (Actor, Scene, or Game)? I think once I figure out where to give it the proper attribute, I'll be able to display it with a Display T

The collide is being checked in the walls. Each wall has a self attribute identifying it specifically. When it overlaps with the line of sight detector, it puts a 1 in a table cell. If it doesn't, it

It uses actors constrained between the player and the enemies, and only fires bullets if there's a clear line of sight. It gets around the problem of the line not detecting the collisions but looking

What I thought I had was this:I made an Integer attribute in the Red Actor, titled Red Score and set it to 0.

I just made an actor constrain its width to a variable function and collide with another actor and you're right... it's not detecting the collision. I suppose this is similar to the fact that Interpo