Next, providing all your Load Attribute Behaviours are in the continue Button, including which scene to continue from, and providing they've all been saved previously, then there should be no reason f

accelerate down for gravity. I normally reference the value to a game attribute though so I can quickly adjust all the actors in the game if needed.

@stevem109 Also, I discovered that if the attribute's value you are using for a Keyboard Input Behaviour is empty, you'll get the dreaded spinning wheel and GSC will freeze.

pressed, use keyboard input (with any available attribute... I used Game.Name or Game.Time)... 3)Preview... touch actor... it looks good at this point 4) Hit Done. 5) Go to the scene icon at the top,

I use an attribute called Accelerate_Offset for the Y Offset, and when the car is steering left or right, I set Accelerate_Offset to be 200, or -200, so that it accelerates towards the left or right a

change attribute: game.unlock To: game.unlock+1

thought I may have to replace these here by the Constrain Attribute behaviour as well? I tried but if I do that it won't move at all.

Yeah I saw that file in the other thread! Tried it too but still "lagging". The constrain attribute is definitely the culprit, the "handling" from the new file work

once they are all over each other, when i try to move the top later, on touch, it is grabbing all the shapes and moving them all at once (I think I may be able to add an attribute to determine which o

Here, I've made you a quick endless bounce that is very efficient (only uses a single constrain rule) and always bounces to the same height . . . .

How do i get the acceleration.y attribute?

Game Attributes

Sure non visible is better but is it possible to turn it on again with change attribute?

Constrain Y position to: AAA*cos(game.Time *BBB)+CCC

Example: I have a single Car actor. In order to have it look and act the way I want to, I have the Car actor itself with all controls and collisions, a Headlight and Tail light graphic constrained to

Move attribute: direction = 0,0° (this equals to going to the right) relative to: actor; move type: additive (also tried stacked, see no difference)

The other way would be to a timer and change the images one after the other using an attribute... you might have more luck here, strangely...

Don't have the rule for bullet counting on the "trigger" button. Add it instead to the bullet actor. Specifically, the bullet actor should have a Change Attribute game.bullet to ga

I tried using the accelerate but now comes the second problem already. My player basically gets outside of the window / image. For every move (left, right, up, down) I have set an attribute self.Posit

A quick rundown of how I added the score... I created a "Bullet" Integer on the "Game" tab. Then, I have a "Change Attribute" command each time t