I am using the Move To behavior when it reaches an attribute called Direction is = to 3.

Yeah, I imagined it could be the self attribute causing the problem.

I am using the Move To behavior when it reaches an attribute called Direction is = to 3.

Shane that sounds spot on. It makes sense, basically had te same setup but without the speed attribute.

Ok make these attributes.

Obviously you have to create and and constrain the camera origins to those camera offset attributes or do your expression from an unlocked instance. Be sure you get those parenthesis in there right to

have a rule that says when mouse button is down, constrain attribute self.position.X to Devices.mouse.position.X and the same with the Y. So wherever I click my character goes. How would I do the stu

Game Attributes:

Constrain a global attribute to the x and y of that actor or position similar, and the constrain the x and y of the gun to that global att. I can try to do it for free, send the file to redsox360blog@

There's a way to store 30 or more Boolean attributes in one integer, and if you take the time to figure it out it can save a lot of effort setting up attribs:

How much memory does an attribute take up anyway?

Yep just use a change attribute behavior and change attribute device. audio. music. volume to whatever you like. 0 is muted and 1 is full volume

Attributes

When i say 'it' I mean the integer attribute.

Hmm...one more question: Will it work to have 80 load attribute behaviors in one actor, in the same scene? That seems like a lot of behaviors...

Okay, I realized it is the Move To Attribute that seem s to be a little sporadic, but it also might be me. For some reason it just won't read for some of my actors.

collisions seem to be messed up for my game too. I get a different result in the web preview than I do in the GS Creator's built in preview mode.

After further investigation, I believe it might be the Move To Attribute. Once I turned it to the Move Attribute, it worked, but not giving me the affect I need.

It would go something like this. Have self attributes in each pieces that have the correct x and y positions. So correctx set to the right x, and correcty set to the right y

The camera origin is constrained x and y to an attribute.