Have a Boolean attribute called change scene.

Make an integer (game.TargetID) & 7 real game.attributes (for X&Y coords)

So for example each actor is given a own unique ID. Using tables that information is stored. It also has two other attributes, col and row. This tells it where it is on the game and where it is on the

When I come back from pause my touch I actor want's to keep resetting to 0x 0y when I touch it. Doesn't happen to touch 2. I've tried everything drag attribute, zero timer and even rebuilt the actor

The rest can be done, but it's not at all easy. I just built a real-time demo that counts down (or up) attribute values. If you get to the point where you need something like that, send me a PM.

I don't use the pause behavior but notice the same thing when rotating the device. Again, a constrain 'fixes' it but you notice a jump in the object positions. So looks kinda glitchy.

For me: If attribute jump is true, or if key "space" (for exemple) is down, and if grounded is true:

chnage attribute

Just note it down that that's what you have done, because once GS fixes the bug, whenever that may be, it could as shown in latest version break your code. However using constrain is very unlikely but

try something like a real attribute, and a combo of on touch press and on touch release rules.

It's bug in the pause behavior. There's always b even an issue the jacks up the camera origins. A way to workaround this is to put a constrain behavior just before the pause behavior to constrain all

(Quote)

I add rule if device scene size with 480. Change attribute to 480. Now why all my scenes has black Corp on the left size?

self attribute.

Just make do with Custom Attributes. Create a Boolean Attribute (eg. 'showHint' == "false"). When Touch is Pressed, Change Attribute 'showHint' to "true." And then

- "Gravity" on actors via an acceleration attribute.

I see. That makes sense. The rule is not really listening for a change in the attribute value. It's just geting evaluated (every frame, I assume) to see if it's true or not. And the rule only fire

Attribute starts at zero. Rule checks when attribute != 0.

a rule in it that responds to changes in a game attribute value, screen_num. The value is changed by hotspots that the user clicks. The rule has a behavior that moves the camera origin.x so that th

If the IAP was used for adding coins, you'd just add to the attribute when they used the IAP