the program notices a change in condition of an attribute and triggering of a rule. Especially when you make a rule based on a condition of anything as MotherHoose described, it is looped (scanned) a

That doesnt look to be a bug. Check if the attribute Movable is unselected in the Actor.

gameAttributes: playerX; playerY

One way I'd do this is make a two new attributes, the first one a boolean to act as a toggle; and a second one an integer for the loop. Set this to the amount of times your actor goes back and forth

Now I have a button and an attribute in my game I want that if I click the button change the attribute to 1 and click again it change to -1

So ill explain what I'm trying to achieve. The game will save the system time to an attribute regularly . so that when the game is reopened it checks the time last saved and compares it with current t

(Quote)

Make an attribute called 'offset' (type = integer or real)

By constraining actors, I meant using a constrain behavior to constantly update an actor's X coordinate, Y coordinate, and rotation -- to another actor's x, y and rotation. It will constantly do it j

Create a game attribute

Your first idea is technically do-able. However, constraining at least three actors to a central actor can really start sucking up the processing power. And the frame rate starts to go south pretty

Title pretty much says it all. Is there a video tutorial out there showing how to do so? Or if it is simple enough to explain in words that would be in great help to me!

I've not had a problem tweeting a single image directly, but tweeting an image with an attribute doesn't work. Support are aware.

The only other way I can think of is to constrain colored actors to the sides of the shapes -- so that you could check to if certain colored actors are colliding.

In Actor 1: (Make an attribute called newAngle. It can be type index, angle, real, or integer.

I found something like min / max in expression ediitor. max set the minimal number that can an attribute contain. Very usefull! E.x. Change attribute:Life > max(1, 50-100) - the attribute Life

@GhostShipApps ... I would think that if you wanted an exact change in B related to A then have Attribute OLDA and NEWA and make b=b+(OLDA-NEWA) so for example.

if you have a left middle and end like i do you could make the middle and end platforms move slightly faster but constrain to the correct movement as soon as they bump into the leading platform to mak

You are totally right and can be solved that way, but at the same time I am trying to learn how to do inverse proportion in the expression editor. Basically to make an attribute increase or decrease i

How to keep attributes that goes into integer table always positive?