(Quote)

Try putting it on another layer, perhaps. I've not seen this template so I'm only guessing, though.

Everything works beautifully until I start adding actors or images over the top.

(Quote)

A timer resets the every x whenever the rule it's in changes condition. Why the need to destroy them, even if you want to avoid using self.Time?

ok I see but if the GS timer would have recognized that we had changed the attribute that is in use for the timer then there would be no need for destroy and respawn in this situation.

----Destroy

(only one timer is needed but must destroy and respawn for the GS timer to recognize the changed value of SpawnTimer)

You can save attribute data in two ways, one is via the save behaviors and also using a table. Most of us use tables. But if you only want to save the one top highscore you can use the save behavior.

(Quote)

got a nice top 10 highscore template here

and when it collides with land, i want to destroy it and create two actors (2 halves) in its place.

It has been stated on multiple occasions that GameSalad are aware of the issue and are actively seeking to fix it. It's one of the top priorities right now.

It's said to help somewhat . . . . but the thing that will really cause (and cure) lag is layer order, GS scans the layers (counterintuitively) from bottom to top, so if you have - for example 30 laye

Destroy

One way to workaround the issue is to destroy and respawn the actor that use the every-timer, that solution is ugly but it works. Even using a constrained attribute as a value for the every-timer does

on Android. Depending on where in the layer structure your actor is it might not trigger rules making games buggy or plain unusable. Opening a GameSalad game for only a second will keep the device on

I guess you could make an actor that is blurred in photo editor then overlay that actor on top of your original actor, and change that blurred actor's alpha to create some sort of fake blurred effect.

The top 3 diagrams show your hero rotating, but enemy is facing 90(Red). The blue (angle to enemy) is 0 in all 3. 90-0+90 = 180 in all 3 which is correct since you should see the left side of enemy in

Use Magnitude to check how far away they are from each other, if you don't know how to use magnitude use the search bar top right.