timer - every .1 seconds - change attribute self.angle to self.angle + 1

You would have to constrain the position of your orbiting (satellite) actor to a set distance from your main (anchor) actor.. Using sin/cos you can calculate this. First you need to store the x and

When attribute game.MusicList = ABCD

Well if you're gonna change it every 0 seconds just change the actors image using the Change image attribute. Or you can go manually using the change attribute and by going down to self.image then cha

Is it possible to constrain an actor to a point on a rotating actor?

Change Attribute:

sounds good to me. If you have a change attribute behaviour say at the start of your game when everything is loading then everytime the player restarts it will update the total score and you can have

i'd say a local attribute for that enemy then?

I'd like to make an attribute that records the player's total game score.

Well, actually, that's kind of what I want to avoid. I don't want some game attribute telling all 23 enemies to throw their spears at some random crate or mushroom ahead or behind them.

i'd say create a new boolean attribute and if it is set to true then have it do one thing and if false then do the other. you could name the attribute like something is_left or is_right, whichever yo

also keep in mind scene attributes can only be accessed from a unlocked actor in the scene

Wait, what exactly is the difference between a scene and a game attribute?

The only thing I can think of is creating a game.attribute for each instance of this enemy actor, and create several instances of the knife, each corresponding to a separate instance of the actor. Is

Hi, scene attributes values are forgotten once you've left the scene; so if you revisited a scene, the original values only would apply.

If Mask overlaps or collides with actor with tag wall change canFlip to true (now open up otherwise) and do a change attribute canFlip = false.

Are there any benefits to using scene attributes over game attribute.

Saving would involve a whole bunch of attributes (as many as the amount of squares on the grid) and so the positions of each tile on the grid can update an attribute that can be Saved then Loaded.

or whatever, that is what the "Save attribute" and "Load attribute" behaviors are for. You can keep track of high scores and any other attributes you save. Just ne

I tried a preliminary non-pause behavior approach.. where i tried to load an attribute to a temp attribute.. then blanking out the speed to 0.. then try and recall that info when resuming.. but from