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

We are in the beginnings of working on a game that has one actor passing over another, triggering an attribute to go to true, otherwise be false.

This will be done on the image(actor which i want to constrain correct)

i know you will have to create a save and load attribute as well at the end so it keeps the score, but i need to know how to set this up, i have the general idea on how to do it, but i need to just c

Change Attribute: self.Position.X

Hi @matarua I can confirm that I had this problem not long ago, and did inform GS Support… I think it's a bug that's crept in as well…gotta be, hasn't it…. a self attribute should be concerned with &a

So I just broke my actors by deleting a self.attribute on another actor - the expression replaced 'self.rotateSpeed' to ' 0 '

is a rule for each sound triggered by an index attribute created by the column in the selected table row.

what is the attribute in the rule?

(Quote)

much easier than adding dozens of individual attributes. Two things come to mind:

GameGenius1,000,000: "Hey guys, got a couple of rockets like fighting and !@#$% and like one is meant to be like kind getting points and !@#$% and like it was meant to be 500 points or somethin

. . . place: Change attribute game.Up Pressed to false.

(Quote)

There's a really good template in the initial box that appears when you open GSC, under Open Recent Projects, it's called Platformer Template. I recommend you open that and study the Rules, you'll lea

(Quote)

Yes this is very possible. Go to your actor and make an attribute in him called taps (do this by going into the actor and then hitting th plus sign under the actors attributes- i.e. position, size, co

Make an Integer Attribute called Taps, then on the actor do a rule when touch is pressed add 1 to Taps. Do another rule that says when Taps = 3, destory the actor.

Make an attribute.