Also note > I used this to convert from iPad to iPhone/Android. I have an attribute called "isPad". When this is false it will enable the dynamic changes.

Your suggestion does work, but it does not work for specific levels. I can make a display attribute for every level, but i have a ton of levels. Is there a way to get around making all those attribute

This sounds good, but I cannot find any attributes to manipulate the camera outside of the control camera behavior. I made an attribute to keep track of the projectiles x position (don't need one for

Just make a rule that says: If attribute stars (the attribute that displays the number of stars) = 1 Display image 1 star (the name of the picture with 1 star)

No, they are not scene attributes. My attribute that counts the stars in my levels is a global attribute, and so is my attribute to display the stars.

After a long journey, i almost have my star system working. All i need to do now is to make the star display function for each SPECIFIC level. Right now whenever i obtain a star in a level it affects

It works, but one important change attribute is still blank. When I try to edit the prototype to fix that change attribute, all of the rules go blank (Image)

Constrain attribute self.motion.linear velocity X and Y to 0.

i think i got it to work, i created a new attribute called full breath, and then said when player collides with bubble change attribute game.breath to game.fullbreath

It's hard to answer this question without seeing your code but I'll give it a go. Does your breath bar rely on an attribute?

I think I finally figured it out. I wasn't taking into account the enemy the player was colliding with. Added a change attribute to subtract 1 from the enemy count and game seems to be moving properly

this usually happens when you either delete an attribute that was used in the rules, or copy the rule from one actor to another when a local (self) attribute is used.

ToonBoom will not do any code/physics related work for you it is pnly a visual tool. Gamesalad is where you will have to deal with collisions etc. If your characters are square that will work well wit

bug with Angular Velocity, in that whenever that attribute is called, it returns the degrees per frame instead of the degrees per second.

Currently, my cars works using the attributes... I constrain all of these...

EDIT: It doesen't work. There are blank spots in expression editor, and for some reason I'm getting rules that say "When attribute _______overlaps or collides with actor"

Try using move instead of accelorate. Unless you want it to continually get faster. But maybe you could use move and for the speed use an attribute called speed and use timers to continually add speed

Change Attribute self.Size.Height to self.Size.Height+2

Make an attribute; theDistance

Make two game-level attributes; newX and newY