I would use a combination of what DanielA suggested and the self attribute you mention. Create a boolean state in the actor called myState (or whatever you want) and set the default value (false if t

Create a game boolean attribute called `touched`.

change attribute game.???? to (game.????+1)%2

change attribute game.???? to (game.????+1)%2

I have my actors set to move with my mouse; ie, when touch is inside, constrain to mouse position.

if you're already setting the image and size once your random value is determined, why not add an attribute for the value when destroyed and set that at the same time?

Although i often find that it is to do with attributes,

That "change" expression works on a boolean attribute? I could have sworn that I did something like that and it worked, but then I read somewhere on the forum that said GS's boolean

You only need 1 gun actor. The gun actor would set a game.attribute with the direction the ball would shoot.

As for changing attributes, (it varies a little depending n exactly what you want to do)

I would like to change another actors attribute by the pressing of a button, ie pic, colour, size.

if I'm wrong, it probably would be hard to add an integer attribute and change it to the number associated with the image selected. then you can use that integer as a multiplier for your scoring syste

I would set it up so that touch the actor change attribute true then spawn another actorthat looks the same. Destroy old actor. The new actor will have the same set up except touch is pressed change f

I want to be able to touch an actor once and turn a boolean attribute true, then touch it again and turn it false. Basically every touch turns it on then off, then on again

particles do not deal with any game rules or collisions, so there is a slightly lower burden on the processor. however, particles are kinda pre-loaded with a bunch of mandatory logic pertaining to th

alter its own logic based on the state of an attribute in the button directly across the grid from it. I plan to do this by going into the instance and building my logic there (as I can see all of th

if there is only going to be 1 "hit" at a time, you can tell the gun involved in the collision to write the associated angle value to a game level angle attribute. then, in the ball

another thing is when you have a huge list of attributes, it gets kind of boring trying to find that one attribute from the whole list. so if at least the attribute browser could remember when you res

The timer is set for say 6:00 minutes (but can be different depending on what was chosen) and is set as an integer attribute (game.timer)

Instead, could you just create a custom actor attribute (integer) for these enemies called "points_on_hit" (or similar) and then change that value each time you change the image? Upo