One more quick note- If you combine my solution above with attributes it becomes even more useful. For example- when actor x overlaps with invisible actor in slot 2, set attribute boolean x to be true

Is it normal for it to forget attributes that have been saved when you kill the app on the multitasking bar (e.g. high scores reset to 0)? If this is not normal, It might be because I installed the ad

So would you suggest just checking for the actor coming to a "near standstill", and then constraining it to that X,Y position, as suggested above?

Have a boolean attribute animate-actor1

Set the TableCellValue to a self.attribute then use that to create the greater than 0 rule.

I am currently using way too many game integer attributes to keep track of the inventory's weapon amounts in my game.. I've been seeing all over the forum people saying to use tables instead of attrib

Give each ball a static index. BallIndex 1, 2, etc. Then, create a rule that when they collide with the character change the global attribute (call it, BallTouchIndex) to the current ballIndex.

When attribute: self.Position X = (End point)

What we are often running in when developing scenes with multiple people is that sometimes we have to look for places where attributes/tables are modified.

Make a game attribute named trackspeed.

Normally you would work by constraining the X and Y position to an attribute modified bi the cos an sin functions.

Oh, durp... You would still need to utilize Tesseract's attribute to keep it from going over.

Try making a display text over that actor with the same code that you're using for the change attribute, and see what this displays. You know your code will be properly done when the text that is disp

You also might try this: Create a new integer attribute called lives in the "game attributes". Then, in your heart character, create six separate rules. Each rule checks to see wh

-Change Attribute-

For the help, I get what you mean using tables, however the equation was just an example to show that there is a way it could be done using change attribute.

Oh and put the change attribute behaviour in a timer-every 0 seconds-run to completion. This might be all that you're missing.

Therefor all you gotta do is have a text attribute for the colour that is changed between "Red" and "Blue" then have a integer for the count.

--Attribute (self.Position.Y) < (200)

So I was hoping I called used change attribute function. And say change self.image to what ever game.colour is and whatever game.count is. This way it will be only a few rules. If you get what I mean.