(Quote)

attribute and set the speed to 0, you could try constraining motion but there's really no need IMO.

If you want something to move, you constrain to X/Y and untick fixed.

that is toggling its value somehow and causing a constrain behavior to only trigger part of the time. But that's a bit of a wild guess really.

I would like to have an actor's color change based on the number of touch like:

on top of each other. I combatted this with a constrain attribute for position Y. But now when they collide, The obstacles rotate in a way while keeping their constrained Y attribute, but avoiding co

entry. If I create 2 rules in the actor Change attribute - self.motion.linear velocity x to AAA and Change attribute - self.motion.linear velocity y to AAA, then this will work. However, that means t

Actor positions are real (self.Position.X is a real attribute) but you can use either. If you plan to always have your actors on a whole number (x=4 not x=4.155) then use an integer.

I would constrain the game over actors y, to some number + camera origin y.

Each key stores a single attribute value and must therefore be a unique name. If you're planning to save and load more than a couple attributes it pays to use a table instead.

Constrain Att.:

as the issue at hand, why using a copy table attribute wont allow the numbers to pull from the table after the scene has reset...

Maybe an animation sequence will work and constrain it to the direction?

Attributes

Everything was okay till I made an integer attribute called "HighScore" and then made an actor called HighScore in which i have the following: If game.Score > game.HighScore t

You are using an attribute called self.time, which is set to zero - and I can see no obvious way in which it is being incremented in any way, so it will always be 0 (so the condition of the rule with

Change attribute game.randominteger to random (1,15)

Everything solved!! Yes! EVERY load and save attribute behaviour "key" section MUST be filled directly! It is a common mistake as @gingagaming said in another post.

I deleted all Load Attribute behaviours for the Lives and that seems to have solved the problem but only for the Lives.

(Quote)