Instead of having actor whit images, you should have them with a VERY small image, and a Change ATTRIBUTE, self image to : The image.

click the "e" to bring up the expression editor and then click on the button that has a downward arrow, click game, then click on the game.attribute you want to display.

Is it possible to use the display text to do something like this

and make the waypoints inviisble. Just don't use constrain's in the waypoint (use change attributes instead).

Start with a self.attribute: self.path (integer type)

Usually what I do is I make a group with 4 change attributes. 2 of them for with and hight, and the other for self position x and y. when I make a game, I usually start with iphone, then go to iPad

Will changing an attribute with a timer create the same growing effect as interpolate?

Try this. Make a game attibute "destroyID" and a self.ID attribute on actor and compare its value on actor touches. Make a rule:

Is this the right way to save the score to unlock other levels? I made an invisible actor in every scene to save the attributes with a unique key....then I made an other actor in the menu only to load

well thats how interpolate works. It wont detect any collision until it reaches its target variable. If you want continuous collision detection while changing size i suggest you use change attribute b

use attributes:

I just implemented the control system for having an actor constrain to the mouse with an offset. Took my less than 20 minutes to DL the software and set up a test scene!

OK So i think i've figured out what the problem was. I was not using the "Spawn Attribute" behaviour properly.

i basically add a number to an integer attribute every time a new level is unlocked - it makes it easier to set up i guess. saw it in a tutorial and wanted to try it out.

Haha shoot >:-/ I just made it so that you CAN'T do that in Garfy 2. I used a single attribute menu system as a posed to having individual ones

Also, as long as they don't have collisions or play a part in the game, then turn Moveable off to save a bit of memory.

Make an attribute (game.jump)

Change Attribute game.Att To ((game.Att + 1)%3)

I really like using OTHERWISE because it keeps things nice and neat. The attributes are integer attributes. I use a lot of OTHERWISE when I've got other integer attributes that do various things based

yeah dont use otherwise. just make sepertate rules when attribute=1 change image to image1 then another rul when attribute =2 change image to image to and keep going wiht the rules