so basically, attribute is something that is constantly running? and a behavior is something that has to be triggered by the user (rule) to perform specific actions?

I can see where rotate attribute would want the actor to rotate all the time. I would use the behavior after a separate function had taken place personally.

Okay, now its a matter of getting use to using the change tables attribute and any other table related expression.

I saw a tutorial and the guy used rotate attribute for an actor to rotate automatically, i thought why not use the rotate behavior instead?

I looked at it again and I see no reason for that. Unless the velocity game attribute was being changed somehow, it shouldn't do that. And I watched the attribute and didn't see it changed from 1000

I know other people have figured this out before but I think they've used a different method. I've always found it hard to get this working until I thought of the way a metronome works and applied t…

Detect attribute value change

You can use other actors' self attributes if you unlock one of the actors. But that won't work if you are spawning actors and it's also not the method I used in the health bar demo.

type of actor -- is that you have to use a game attribute for the character's health. But that's a minor thing.

@Tatiang: Ah, thanks! I've been putting the damage attributes on the character themselves, I thought it be simpler that way.

Finally sprite collision - I'm using the standard collision attribute in Gamesalad, and tried it as both rectangle and circle, but due to the main sprite having big ears poking upwards a fair way off

     Change attribute game.playerHealth to game.playerHealth - 1

Make an attribute, integer, value 1.

Hello guys, I was wondering if it is possible to rotate the image of an actor. I know there is an attribute called rotation but the problem is that this attribute is not working properly on Universal

To answer your first question, it doesn't matter too much but one thing to keep in mind is that the Change Table Value behavior takes a single row attribute/expression but can have many column values.

I probably did something very stupid, but I wanna see if there's a way to fix this, I tried changing an attribute type in the .xml file of an actor, since I heard you were able to do that, but ever si

Examples: A 'real' attribute could store a precise location on the screen, an integer would be quantized to the nearest pixel. If you had a game where a ball had to bounce to a certain height, the bal

so I was wondering if there is a good source/tutorial that goes into more detail about these different types of attributes named in the discussion title, and different instances in which you would cho

(Quote)

Actually, now that I've watched the video I wouldn't use collisions at all. I'd use tables and Interpolate the movements.