Are you using an Animate behavior? Are you doing anything with tables or Change/Constrain Attribute behaviors with regard to the actor's self.Image attribute?

I don't know and make my own formulas and attributes at this point. If you look back through my history of forum threads (as with most guys starting out) the questions have gotten much less tedious a

(Quote)

     When Attribute self.toggle (integer or boolean) is 0

Example (attached), I've changed the numbers at the end of the function to the mouse's X and Y position attributes, now the floating square follows the mouse.

If you know how attributes work (an attribute can be any value you want) you should be able to see that you can replace any (or all!) of the values in the equations with an attribute that you can cont

. . . those two lines could be a change attribute behaviour or even two interpolate behaviours, but basically you click on a hexagon adjacent to your current position and you will jump (or slide) to y

If you reset scene, you have to manually reset the attribute back to default.

Yep. The board could be a single image and all of the rules check to see if an actor is at a precise point along some set path(s). So if you calculated all of the centers of the hexagons and put the

(Quote)

You don't really need to duplicate attributes, there is already an attribute called rotation so there's no real need to make another one - and introduce an unnecessary Constrain behaviour (the fewer C

     Change Attribute self.Item Number Select to mod(self.Item Number Select,10)+1

I have a game where the majority of the gameplay takes place in one scene. I have a number of enemies that get randomly spawned and many of them use hitboxes, so I have a rule set up to let each enemy

Well thats the idea but the logic to create it is the struggle.. i gave it a go..made an attribute lander-rotation constrained to the actors rotation..then in the landing pads logic..made a couple of

Create the same game attribute (boolean is fine) to control when they are allowed to move.

Create a game level attribute to control when they move (optional). Since we only need this attribute to toggle between two states a boolean attribute will be just fine.

Constrain X position to: 22 *sin( self.Time * SPEED) *sin( self.Time * SPEED)+512

(Quote)

It doesn't matter if it's an index or integer attribute. Either type will support values between 1 and the number of rows in your table. I generally don't use index values because they aren't suppor

It's not really enough to describe a rule. For example, the image change could be done with Change Image, Change Attribute, Constrain Attribute, etc. Likewise, the movement rules could have conditio