Attributes -

Woke up this morning with an optimization idea: Know how it is that people tend to recommend minimizing the number of constraints in your project, and it was nagging me that I already have 7 constrain

The suggestion to utilize 'change attribute' instead of 'constrain attribute' fixed the problem.

Or you might want to 'change variable' instead of 'constrain variable'

Make an attribute called gravitee, set it to 230.

Or use the change image attribute (Image)

Constrain Var1 = Ran(1,3)*1000

If you need collisions to work while resizing, I would use a Timer and a Change Attribute behavior instead..

constrain attribute position Y = Offset height + ((current_health/max_health)*50)

that way collisions only happen if alpha is greater than 0, i.e. visible.

Okay, I've solved it for the most part. I've updated the template with the solution (so far). I am still having some issues with the collisions (making the pips "moveable" so they

I believe we have a great and growing community here and I do hope that we see more examples of folks sharing 'hunches' on what might work with GS and seeing more 'collisions' take place that will bir

I suggested the creation of an invisible actor that is constrained to the offset of the zoom.

You can then save the names in a text attribute.

- create a self.previousXvel (integer attribute)

So I've got a game.speed (interger) attribute and I want it to speed up by +5 every 15 seconds or so.

Is it possible to have an AttributeName recognized in your Rules by combining two Attributes?

`constrain attribute game.score to exp(self.position.X/477.72393009357)`

I followed your instructions about creating a highest score page when my game ends. I have two integers - game score - high score and a change/ save attribute etc...

Sorry i had a quick look and it was the change attribute, mines sort of like this