." I dont want the rock actor to destroy after it hits the character. The problem is if the character is touching one rock when it gets hit by another, the health will not go down because i

(Quote)

(Quote)

A bigger board is the most requested thing from players. I don't really understand why, but it seems to be first thing players say. A bigger is easier enough to do. Then the request continue that a ne

(Quote)

Hmm if they are within the scene area they should not disappear. Once you spawn the. To a spot on the screen they should stay until you destroy them. Anytime you build something scrolling in creator y

* Option to add a timer using the button at teh top of an actor's behaviours, like we can on Mac with Rule and Group.

@Hopscotch @Lost_Oasis_Games I added more height but I think I hit a stinker. If I'm not mistaken the added size is placed to the top which means I need to offset all my content up so I can actually u

I dont really understand what you did , but if you want to destroy an actor based on other actors attribute use game attributes instead of self attributes.

So far I managed to display a key, which gets "destroyed" when clicked on and gets "spawned" at the bottom (like in an inventory). Also when clicking on the key in

Submit you're score to the world rankings on Game-Centre to see if you're the top on the Auto-Bahn leader board. Alternatively, you can tweet your score and challenge your friends.

You need to watch how you spawn and your layer order. See the explanation George posted in the release thread.

Bug:1671 Actor in lowest position of lowest layer flickers

* Create a rule inside the spike... if spike actor X position => a specified distance in X off screen - destroy this actor.

* Selected at Taipei Game Show Indie Game Award Top 10 Game

@GeorgeGS Thanks for that info, I went and changed all actors to spawn at the front of the layer, although I haven't tested on android yet, in creator, the enemies spawn without even causing a bit of

You need to place the buttons on a separate layer to all your other game elements, and then in the layers view make sure 'scrollable' is unchecked (no tick) for this layer.

list bigger, so depending on which front/back layer/actor option you use you get different behavior.

Here off the top of my head, not at a GS machine right now...

The second problem is going to be related to how you have the rule set up for destroying the actor. I don't have time now to look at your project file but adding a screenshot might be a quicker metho