If the actor is spawned in the back of the bottom layer, it would not cover anything up.

Perhaps but bare in mind that there will multiple actors that can collide in many different colours. IF I spawn actor at the back of the scene. I would then have the next collision not showing since …

I'm guessing that's what the heart at the top is for. It was ticking down even when I wasn't being hit. The heart at the top and the health bar at the bottom is definitely confusing. Maybe change the

(Quote)

(Quote)

your sides/wall indicate isometric perspective but your figure remains always top down

You can do it with a separate actor that will be spawned to the back of the layer at the point of collision. In that actor you can have it change to the color you want, and have it change its size (&a

* Destroy enemies by touching them with your finger

+the number in the background is cut at the upper top

Put a new line after the the <?php line at the top and type in

(Quote)

(Quote)

(Quote)

Lowest layer first > Lowest actor within that layer > Topmost code first within that actor.

One question about your Fast Constrain v2, why does the child disappeared if I move it to the lower layer than the parent?

(Quote)

I wanted to add that on top of the integer method that was suggested, which is the most optimal. Using the "else"{windows} or "Otherwise"{Mac} part of the rule set

Katz the Samurai is running across the city rooftops, trying to catch her enemies! Guide her through the endless rows of skyscrapers avoiding falls, planted bombs and flying saws!

Is the actor spawner on a non-scrollable layer?

It is in essence, a laser beam. That's supposed to stop spawning more laser beam parts when it hits a 'floor' piece. That logic is sound - if it his a floor object, that section of the laser destroy