I guess there's an easy solution to that problem with the attribute, but I tried several things with the angle attribute but it's not working...

No way to sort that I know of. Someone was saying they just use 1 thru 500 for example as the attribute names then keep a notebook with what each number is actually for. i've never had that many so no

Thanks, nobody gone higher than about 500 yet then? Also is there a way to sort your game attributes a bit? Like move them up and down in the attribute list?

will determine wether you want to create a game attribute or self attribute. if you plan on making an iphone game I would go ahead and create it as a game attribute and put the key rule inside you bu

oh that is a made attribute i guess

Hey guys, I have one more problem. I can't find the animate attribute.

--Change Attribute self.animate to true

create a game.Attribute boolean call it keyPressed

Yes you can achieve different shapes very nicely as long as they are not moving. If they are going to move they will need alot of constrain attributes which can be very resource intensive if you have

The key just refers to a keyword so yo can remember it. It can be whatever you want. you just save and load the same attribute

I am not really understanding this save "key" business. Can I save multiple attributes all to just 1 key, such as game save 1, game save 2, etc...? Or do I have to make a key for eve

LOL! YES! your game.Attribute "Humor" has its boolean permanently set to True!

...Weird huh? Is it my attributes?

for the issue when you hit preview, it sounds like you have a bad attribute or rule. did you delete any attributes (global or actor) or copy rules between actors recently? double check EVERYTHING in t

Create Actor Attribute

Make 2 attributes call them player x and player y or whatever you want. Have them set to the starting x and y positions in actor 1. In the actor 1 have a 2 change attribute behaviors change self posit

in mine the gray actor has 2 change attributes to a circlex and y. then a little 4x4 invisible actor in it.

I needed unmovable objects when I moved a bomb and placed it down .. but then moveable objects when it exploded. I created Actors with movable off and then when the bomb triggered a detonate attribute

when actor1 overlaps or collides with actor2 change attribute self.movable = 0

I memorize the level won thanks to behavior "Save / Load Attribute" (VARIABLE: nLevelFinish).