change attribute: game lvl speed to 2

so you make it as a game attribute not a self attribute. we explained the differences above. Instead of creating the attribute inside the actor you go to your scene click the attributes tab on the top

pops up and you enter a number such as 2. The attributes for this are always set at 1 until they are changed by the user. My problem is that the number the user enters is not factored into the equati

that means the person made it themselves for the project. Self means its a self attribute inside the actual actor your working in. If it says game in front of it its a game attributge

when attribute score is greater then or equal to 1000

when attribute score is greater then or equal to 1000

No, just make an attribute for the actor, not a game attribute.

Then make an ACTOR attribute also named hitpoints? Maybe name the actor attribute myhitpoints to cause less confusion? That wouldn't affect it, would it?

Make an attribute in that actor that is an integer call it hitpoints and set it to 4.

I've added a self attribute to my hero called active and added extra conditions in my rules to say only work when active is true.

I'm guessing you create an integer attribute you could name 'hitpoints' in the actor and set it to change that attribute +1 every time it gets hit. And then have another attribute (most probably a boo

are the same moment so I can't use a game level attribute to say 'actor-touched' . Have any ideas?? Thanks, i'm racking my brains on this and don't want to have to change the actor rules so that the

Change Attribute self.Motion.Linear Velocity.X To: 0

If you want to constrain the paddle's Y position do this-

Do you use rotate to move the paddle or is it animated? If you don't use rotate you can turn physics off which will stop it moving down. Otherwise try a higher density or constrain the paddle to a fix

Any thoughts on why my player/paddle is being knocked back at launch and sliding away after other collisions?

ChangeAttribute

like tendrmer said theres issues with timers and stuff but you can try this. insted of doing when attribute count is less then or =0 change count to 0, do this. when attribute count is less then or eq

i have a rule when game, attribute "go" is true , every moving actor on my scene moves, so i have a counter in the scene with a self attribute count=6

you would probably be correct. you need to make sure you are saving an attribute to begin wit and make sure the key you save it to matches exactly how your are loading it. Also Make sure you run the v