You would make the counter in Actor A, and you would use a change attribute behaviour as you describe (change count to count+1)

Would I make it a Change Attribute or a Constrain Attribute? That does make sense, just not exactly sure how to set that up. Would I do it by creating a new counter that isn't visible so I could put:

You could make an attribute within A that counts upwards every time it collides with B. Then refer to that with rules that specify what the colour should be at each stage of the count. If it gets too

Create another actor and constrain the X / Y position to your enemy / hero actor and use them as collision detectors.

I have a list of event names in a table which is imported from a server and I named my images which display event names to match. I am using spawned actors to display the names with a Constrain Attrib

(Quote)

The "Save Attribute" action can be a little unreliable at times. You would be much better of saving and loading your attributes to and from a table. There is plenty of information on

This important so you can load. So make it something you will remember. Let me explain a little bit you save an attribute with a key. Then put in the start scene in a random actor some load behaviors.

when you do save attribute, is has a second section that says "as" does that matter? or will it save it regardless?

If you want to save an attribute simply put the "save attribute" behaviour at the point when u want 2 save it. (Normally after a new score for example) then use the "load be

how do i save attributes? and to what?

Because of the sin() function, the actor interpolates an attribute (like width, angle, position, or color) around and around in a circular pattern.

I am working on a game where the player character is made up of several actors constrained to a hitbox (legs, body, head, arm, arm). The hitbox spawns them into the game and they are constrained rela

@GamesforGood in your actor place a rule with two Constrain Attributes and change these example values to whatever you want.

Then constrain (Image)

[Do change attribute game.shoot hold :to true [change attribute game.shoot :to true]]

Than when game is over turn Star Activation to True. Than in each rule but attribute star activation = true. That should fix your problem of displaying the star. You going to also have to change it to

Using change velocity and change attribute is like the Smash Hit hack. Take a look at it. (Image)

If I use -change velocity and I use game attribute(integer) for -Speed-. It can't realize speed number.I have to write one by one to every change velocity behaviours.

If you use a game attribute, you can change the value and display the value of it in any actor(s).