RULE (inside powerup actor): if actor overlaps or collides with (the other main actor) --- destroy actor, timer: FOR 10 seconds, change attribute game.x2on to true, timer: AFTER 10 seconds, change att

Yeah, for some reason, the boolean attribute is not changing back to false...

I got it to work, but after the 10 seconds are over, the x2 keeps going, although I made sure there was a rule with a timer: after 10 seconds change attribute x2 on to false. Any ideas?

every 0.25 seconds. That aside, I made 2 attributes for the actor, one an Integer the other an Angle. Well, I ment to make both angles, so I went to delete the Integer and it seemed to go away. Bu

Wait, so if use the save attribute and restart the game, the items will still be there?

@developer6810 - not if he uses a save attribute.

You would have to wrap the regular points in a rule that says when attribute game.x2 is false. Sorry, forgot that bit.

You would probably make a boolean attribute and set it to false. Call it x2, or something.

I'm lucky because in my game the camera only rotates when the left or right button is pressed, so I don't need to constrain the invisible buttons to keep them in place, I simply have a rule saying tha

… have the Otherwise: section changeAttribute: self.Image To: that image

Make 4 integer game attributes and call them Aplace, Bplace, Cplace and Dplace. Rename your runners to something like A runner, B runner, etc.

I used the constrain attribute to make a ball, after it is spawned every 3 seconds, chase an actor. If works perfectly during Create/Editor mode. However, in GameSalad Arcade and in the Web Preview, t

Save attribute:

Make the spot you want to save attributes first then give them a key. You then use the load attribute on the first screen of your game and in the load attribute you call that key.

What I'm trying to do is put an attribute inside my enemy actor for his health. Then when the player hits him I want to be able to subtract from that attribute inside the enemy.

make a boolean attribute : ActorTouched

I am trying to do some stuff with targeting and angles. So I made an integer Attribute for my actor. Then I decided that, no, I would prefer it to be an angle atribute. So I hit the minus button an

No worries about more questions; I took it as read that you knew about the Save Attribute Behaviour so my bad...(Quote)

I have a few questions if you don't mind. To begin I understand the first part in which you talk about making a game integer attribute and calling it SceneGo and set its value to 1. Also I understand

Make a game integer attribute and call it SceneGo and set its value to 1.