-Set a timer to reset the boolean attribute to 'False' after:

I have an object with a Boolean attribute titled "falling". When the object isn't touching my 'ground' object, "falling" is true, which starts my linearspeed -50 ac

-Make an boolean attribute in the 'Game' page

@wingmanapps that still did not work for me. It displays the counter, but it does not count up like I am wanting when I replace the game.Time for my new integer attribute

(Quote)

Okay this is a bad memory allocation error. I know GS fixed the issues on their end regarding this so look for an attribute error such as mistakenly putting a number into a Boolean or vise versa. This

from the ground up so they understand why every attribute is created, why each rule is setup the way it is, its an enjoyable process in itself and how I learnt. Also obviously templates made with old

@SoxProcs - It needs to be a real attribute instead of a integer - sorry

Set a game attribute

In the mean time I assume we must use a "Math" actor (with attributes) to access table data, do calculations, and constrain back to the table?

Your constrain attributes sound like they should be working, is Actor 2 possibly checked to be 'not moveable'?

1. I have 2 boolean attributes for movement (1 left, 1 right).

There's a work around, make a self or game attribute then change it to the data from the table then check to see what the attribute returns.

now its slower xD if you want it faster do every 1 second change 'real attribute' to real attribute-1 and start with the real attribute on 10 or something

you can make a real attribute and say every 1 second change 'real attribute' +1(or something you want) and then say every 'real attribute' spawn actor.

Creat an integer attribute. You can call it "HowManySeconds" and set it to 10,for example.

two actors attributes, one to represent "Z^2" and I can use self.X and Self.Y in the expression editor and then store the current least distance in a 2nd actor attribute to compare a

So here is my 2nd option I guess, instead of making 40-80 global variables to compare I could use Self.x (ATTRIBUTE) to check distance to other actors with the following super fun math.

Unfortunately I don't think one Temp attribute would work. That would disallow comparing multiple ranges to each other to find the smallest.

Could you use just one 'temp' attribute? You could reuse it every time you need to access a table value.