Then have a rule setup that interpolates that attribute from 120 to 240 and back again. (or something like that)

about to start properly tackling this, anyone with any prior knowledge had any particularly good way to make it work. Or is it simply lots of attribute tracking...

I'm trying to make a player actor move based on a screen touch action. I have an attribute boolean named Player Movement. Whenever the background detects a touch press, I set the boolean to true. O

Sorry I'm pretty new, I've learned a lot already but I can't really figure out how to have an attribute call to another actor in the way that I am wanting.

Victim doesnt fall threw anymore, and i sent it backed fix. Your collisions and rules might be a cause for some glitches though. Let me know how it is.

---------Change Attribute Self.TouchDistance1 to magnitude( game.Touches.Touch 1.X - game.Touches.Touch 2.X , game.Touches.Touch 1.Y - game.Touches.Touch 2.Y )

I think that when you make it shorter what you should do is put in a timer attribute and in the timer you should but if touch...

Any ideas on the collisions not working right?

Like they said above, theres no simple behavior to do so, but it can be done. I imagine you would use touch 1, and touch 2, then when they overlap or collide (pinch together) change attribute camera t

The following is what I am trying to get to - I amplifier is an attribute that I made - Thanks for your help.

I have a image when attribute (integer) is changed to 1 it will change image.

Just checking you should make your scene height twice the normal, and animate the camera from one to the other, and not have the actors constrained to each other in a normal sized scene, as it will be

I am trying to use the Play Sound attribute, but it keeps saying no value. I do have two m4a's in the music tab, but the play sound will not let me add the sound. Is this a bug?

So, say for example – a bit different from what you require – you wanted a spawned actor to be destroyed when it collides with another actor, you'd have a scene attribute in the second actor which say

I agree: a real-time attribute list would be great, and would save a lot of work.

The GSviewer is no good for testing saved/loaded attribute. To check if it work, publish your game, transfer it to your iPhone and then make the test.

Make a game attribute called "wind" - integer

Save atribute : attribute: game.hscore1; key: hscore1

I suggested a while back to have a real-time attribute list, perhaps as a floating window, that would instantly update all attributes as they changed. Would be great for troubleshooting, I think.

We have sent a message to the support because our game is not working fine anymore. It was a "simple" switch of a boolean attribute (we think it's the problem, but not shure) that wo