To destroy the bad guy, I’ve got the following attribute set:

when actor collides with [portal 1], change attribute [position.x, position.y] to [location of second portal]

yes save attributre. Then you load the attribute when the game starts

When I started figuring out how to implement the "Billie Jean" tiling system, I realized these extra actors would create a lot of problems. Do I really want 40-60 constraints for 20

Rule: attribute receives mouse button down

i was also jacking with it by having in a change attribute instead of the constrain attribute. my 2 attributes for the tracking of the coordinates have been "real" type attributes. a

ok im pretty certain now that the problem is with the constraining attribute

i just tried multiple times trying to get the attributes to constrain. i even tried changing the attributes manually rather than the players position changing it and it did show the position i entered

you dont need to use a transparent image to make a actor invisible. Just set the alpha to zero or uncheck visible under its graphics attribute

when touch count is 2, change global attribute to 1. When global attribute is 1 and touch count is <2, change attribute global attribute to 0 and DO WHATEVER YOU NEED IT TO DO.

That is fantastic, so conversely I can also tell it if mouse position y is greate than 10 and less than 230 constrain to touch! Why oh why did I not see that?

Is it possible to constrain the player to min/max X and Y co-ordinates?

change attribute works great for me cut loading down by half in my game for that scene.

Make an attribute, click count.

Add a counter attribute (real or integer) in the actor

This doesn't make any sense. Change Attribute had the same basic result as Change Image.

You can use the game time attribute

and so on. with the change attribute rule rather then the change image rule the device will not preload those images.

have the actors alpha set to 0 have it wherever onscreen. make a rule when attribute alpha=0 change attribute self position x to random(0,480) and change attribute self position y to random(0,320).

Yep, you need an animation state attribute for each animation - then they will work perfectly (Image)