One way is to use another layer that doesnt scroll and have the you win actor appear when finished in that layer. Another way is to have an attribute “finished”. When actor crosses finish line, change

* inside this tap-to-draw actor, create a rule that says, when "game.attribute.drawunlock = 2, destroy

@Braydon_SFX Love stories like this. Didn't let the immense complexity of these systems and processes stop your creativity. You searched, found, tried, mastered tools, and eventually reached top 500

several of my own games (one which reached the top 500 apps overall on Amazon, which I'm very proud of!), work with hundreds of clients all around the world, and now I get to work for the company tha

Simply use a "Display Text" Behaviour pointing to the Leaderboard Table starting on Row 2 (Row 2 will be your Top Scorer, follow by 3,4,5 etc). Column 2 contains the score and column

either side of the original knife hit, and then destroy it.)

I've been developing apps as a side thing on top of my normal job. However I've not been declaring the tax as income. There hasn't been much in the way of income but over the last year or two it proba

No prob! The challenge i have is when placing new actors, they usually go into my top layer which is unscrollable so i am have to move them after testing and not working right... Always keep layers in

do you have more than one layer? Is one scrollable and one not scrollable? That is when weird things happen for me. The actor has to be in scrollable layer if the scene size is larger than the screen.

I have an enemy layer and a hero layer. both are moveable but the Hero layer was below the enemy layer so i moved it up and boom fixed the issue at least for me.

@tatiang So I read that post and changed up my layers and it is now working correctly. Thank you once again for pointing me in the right direction. Top Notch!!

Another question: should banners be in a non-scrollable layer?

http://forums.gamesalad.com/discussion/88773/collisions-overlapping-not-detected-if-detecting-actor-is-on-lower-layer-than-target

Do layers play a part on collide/destroy for enemy purposes?

If you have the wood on a higher layer than the knives (in front of them), then the knives will appear to be stuck in the wood. But there are so many details that you haven't included -- such as the

* When starting a new project, there are options for starting templates. Nothing changes from that of a blank project. Is this an error? (referring to monster maze, top notch trivia etc)

All my actors have the destroy behaviour very well put (when they surpass a certain amount of pixels south of my hero (I double checked and it works perfectly fine)

At this stage, rather than asking my players to confirm, I have set the game attribute (forgotten the exact name of it off the top of my head) to '0' so that ALL players will not be tracked and will j

(or whatever they say, I don't know off the top of my head.) Then I re-create the attribute and they are in the right spot. A work-a-round is to delete the self attributes once I notice them in the w

The only issue I have is possibly related to other users' missing assets... ...but I added a menu option recently, to turn off/on some cartoon fx in my game for performance reasons, and it's fine in