Is there any relationship between attribute name length and game size or performance? In other words, are long attribute names internally translated into symbols that are efficiently managed, or are t

Try various combinations of timer with acceleration. Basically, if actor is in contact with platform and jump attribute is true, for .1 second accelerate 90 degrees... and after .2 second set jump att

Constrain seems to be working. I have separate attributes for the two different difficulty levels and I changed it on one and it isn't freezing but the other still is, which is what I'd expect. Weird

CONSTRAIN ATTRIBUTE: Game.highscore to game.score

Does having a long attribute name add heavily to the running speed (processor usage), or when it is packaged, would GS not slim things down where it can.

One thing you should always do (if you don't already) is making your attribute names relevant and specific.

First of all...use integer attributes. XY pixel positions are whole numbers ... not decimals. Real attributes allow for decimals/fractions.

I made 2 attributes (real) y and x

the save attribute behavior will also save the value to memory...so it remembers your progress if you turn the game off and come back later.

Rule: attribute = true: change resolution or spawn icon.

Change attribute

the particalRotation attribute should be a "real" value.

ehi synthesis thanks, but for attribute "particleRotation" it is a boolean? real or?? thanks

.......change attribute: self.ImageID = self.ImageID + 1

- I put in the ImageID attributes

key: highscore Attribute game.highscore

in the actor...set a self attribute to ImageID

set a game attribute TotalActorsToDestroy

Create global game attribute: Game.buttonpressed

create two game attributes (integer or real should work) call one jumperX the other jumperY. In the short invisible actor have two constrain attribute behaviors and constrain game.jumperX to self.posi