@DaGreatness its is an easy task to do, though it'll be heavy on the performance end. Either ways, to accomplish such a behaviour. U need to Constrain cam width to cam height and then constrain cam he

Just curious why you can't use the collide attribute? Also, with the jumping, do you mean he can only jump when reaching a certain speed or if you press jump and forward at the same time he jumps forw

The part that makes my game annoying to make for a jump system is that my actor cannot use the collide attribute with the ground, or any platform below my actor. Also, the jump system for my actor can

-- Constrain Attribute: self.Position.X To: max( game.sliderMin ,min( game.sliderMax , game.Mouse.Position.X ))

I did, change attribute > game.Score to 0, and placed it above my Reset Scene...

also place a change attribute scores to 0 (make sure its above the reset scene behavior)

If you don't want to use the standard reset behaviours you will need to go with a similar approach to what @timolapre1998 says. Have an attribute to say if the game needs resetting, and if it's true,

first make a boolean attribute (lets say we call it game.reset)

constrain game.bet to ((money.max-money.min)/300+(money.min/300))*self.position-300

I don't know your values and how to do this exactly but you have to do something with the self.position.x from the money thing something like constrain game.moneyBet to self.position.x/4? so when pos

I´ve constrained it so it doesn´t go to far but I´ve the problem of constraining it to a value. I want the value to be between to values. We can call them moneyMax and moneyMin. But I can´t get it to

No problem. Since you only want one object to know it was touched you can just use the touch count and an attribute to know if a touch is present on the screen and the attribute will tell you if the t

in its host attribute, so it didn't match.

Constrain self position X to: 200*cos( game.Time *200)+ 284

Why don't you do a background with the controls already in (like the 1st link i shown you) and unlock the background and do constrain self.rotation to -scene.camera.rotation.

Yes, you're absolutely right; it can't ever be anything different.... I've no idea why I was thinking game attributes could be "magically" loaded without a load behaviour... so despa

Overlap or collide with barra change attribute self.position.y to 0

Make an attribute Boolean called hidden.

I think that load attribute will always be needed in order to load a saved attribute. It would not work to implement some kind of automatic loading of attributes for several different reasons.

make attribute for the clock (integer=30)