I do tap to play on some things, I do the transparent layer full screen size on top of everything, and create a boolean attribute called START.

i tried this by making a transparent actor full size of scene and one layer below all of the other buttons .... but my problem is that even though other buttons are higher on the layer order, both see

I have no idea why these things are happening. I've followed the tutorials on youtube from top to bottom, yet it doesnt seem to work for me.

@smurfted I mean, you could slice the top image into tiny squares in Photoshop and spawn them in a grid to appear as one image and then upon collision with a small "cursor" actor, de

Btw, another question: Do you know why my actor spawns a white rectangle on top of itself, when i add a custom .json collision shape file?

Can someone please let me know if the Done button text at the top of the screen when using Keyboard Input is blue when an app is properly installed on an app? I only have a Basic account so can't test

self.Position.Y to currentScene.layer.road.Position.Y

(Quote)

(Quote)

true, on an average I guess actors on top are the most important, while the ones in the back are probably background elements and stuff like that. But good to know! I'll try switching things from fron

Yes yes the BOTTOM layer goes first in the scene.

ah wait, I didn't know that. So the layers from the bottom are the first to be processed? But within the actor the instructions are top to bottom, right?

Yea idk, may be a limit to the engine, BUT I do know that Gamesalad processes the layers from BOTTOM FIRST to TOP... so remember that. Since your BACK is a lower layer than the top, maybe have the rul

and one called "back", the layers are ordered as follow:

@Football20 You've already posted an announcement about this. Opening multiple threads on the same subject is not permitted. If you want to bump your original thread to the top, just go and add a new

(Quote)

Put the "destroy" rule outside of the "overlaps or collides" rule and it should work.

(Quote)

Easy way would be to keep track of what room you're in with an integer game attribute, and use that attribute to determine the column in the rule that destroys the gem if it's collected.

(Quote)