You could create one actor with a Display Text Behavior and use a Text Attribute as the text displayed. Just feed the Text Attribute a new line of text each time using a Change Attribute Behavior.

Game attribute: velocity 80 real

(Quote)

(Quote)

Yep there it is. So should I drop it in as a separate change attribute inside the rule "When actor receives event mouse button is down or add it to ....? I'm trying it every way I can think o

(Quote)

Add Camera origin X / Y as a global attribute? I mean I see it in the game attributes, but I can't seem to find it in the expression editor to add it ....

Custom behaviors are just behaviors that you modify and then save by dragging to the custom area. They aren't different behaviors. So for example, I use Change Attribute self.color.alpha to 0 all th

your actors (where applicable) instead of three constrain behaviours.

If you have actors that are not moving, you do not need to use a Constrain behavior. Instead, just change the attribute of one actor's self.Position.X and Y to the other actor's game attributes:

done by using a game.questionNumber (integer) attribute that starts at 1 and gets increased by one each time a question is answered correctly. You then use that attribute in a tableCellValue() funct

I thought you understood that I have moving actor's and 100 other actor's have to constrain all the time to the position of the moving characters.

(Quote)

(Quote)

Adding to what @Braydon_SFX has already said . . . . (basically self.attributes don't transfer)

self.original_height and self.original_width are attributes you created within the actor, not one of the pre-existing self.Size attributes. Unfortunately, if you created a custom behavior that utilize

i attach the self.size to a new attribute i created inside the actor and then i used interpolate to change self.size from small to large with a timer

Under Game Attributes you can find Display Size as an Drop down menu. Is there a way to self create those "folders".

You could constrain each of the RGB channels of your objects to a 'clipped' sine wave (a sine wave with the top and bottom squared off), and then offset each of the channels by 120° . . . . this will

(Quote)