You might be using a constrain attribute behavior when you probably really want a change attribute action.

Essentially the second part beginning with Vector to angle lol. Would these be custom attributes for the constrain rotations?

Constrain Rotation to:

Change attribute game.maxTime to game.maxTime+1

(Quote)

I assume this new attribute is an integer?

(Quote)

in order to get it through. Instead I see an attribute of a file version set at 2.2, I set it to 2.3{the latest sdk version is 2.4}. Re-uploaded it and it went through.

(Quote)

If the system can check on the iap screen wether an item is purchased or not, and if there is a game attribute that checks whether your game has purchased this item or not, if the former is true while

If you are adjusting the timer then you can't* use the built in time attributes (e.g. game.Time). You'll need to use a custom timer, for example:

I just spent half a day resolving a small issue, in the end the solution was to mix constrains and a loop in an actor, all constrains caused one issue, all loops caused a separate issue, after lots an

I have a question about how to reset an attribute and then add 1 to it.

So just know that when I tested a 0.0 sec timer vs constraint attribute (always running) vs Loop while (no conditions), the timer had the least problems and best performance.

I wouldn't say this was the case, whether you are running a timer, a constrain or a loop, there is no distinction between them when it comes to whether they are always running or not . . . if you can

Constrain scene.camera.origin.X to player.pos.X - (scene.size.width/2) + 100

as reading position and velocity and recognizing collisions. It runs at 60fps. It's all about how you write your code and your layer order for that code.

You need to change attribute to attribute+2

(Quote)

You can also do the same thing with: Constrain image to floor( game.Time*30)%21