Constrain Attribute self.Motion.LinearVelocity.X To -scene.Background.drag.Motion.LinearVelocity.X

If your just trying to keep your background in place no matter where in the scene you are, dont constrain it. Put it on a non scrollable layer.

Never mind, Just worked it out, had to constrain it plus 100.

Hey Guys, I am trying to constrain my sky background to the camera view, I've managed to do this with camera origin x in the scene, but when i try to use camera origin y it jumps to a position that sh

Have a game boolean attribute perhaps "Ball_Alive" and set it to false, then inside the ball, have:

Change attribute Coin to 0

I've searched the forums for my particular problem. I'm trying to make an actor speed up every 10 seconds. I created an attribute "time" with an integer value, and set accelerate s

Just so you know If you were going to put actors on each side to act as touch controls, you dont have to constrain them. Just put them on a non scrollable layer.

that specific scene for that instance or make an attribute/rule if level number = 1 .. change scene to scene 1 so on..

While you can recover IAP purchases from the App Store it should be used for recovery and not as a replacement to saving the attributes of your app. When someone unlocks something you probably set som

Would it be to much on the game engine if I were to constrain a controlling actor to each side of the main actor?

Yes, setting an attribute to 100% causes the banner to appear. The banner cannot be controlled (at least to my knowledge)

Attribute - game.Touches.Touch 1.Y > self.position.Y

Well, the actors are the parts. I'm using a constrain attribute to make them stick together. What i want to know is if i can have the selected actors spawn in a new scene with a new set of command rul

@MarkOnTheIron - your method works perfectly! All I have to do is add the self.ID for each instance to the key and it works! I don't think this will work for spawned actors, but I can have a bunch of

And saves the attributes.

Oh sorry... i ment RIGHT, (not left). This is so strange. I think I´m missing some constrain attributes rules for the position of the actors or something, but I`ve tried everything I can think of.

You need to use a Boolean attribute to return control to your hero. Your hero should have the control camera inside a rule that says when Boolean is true control camera and have it so that when the c

In your fork and spoon actors, create a boolean attribute called self.moved. If the player moves/selects a fork, have that actor change attribute self.moved to self.moved = true. Then when you displ

Use a rule set to When actor collides with [dark green actor] change attribute...