And then we have the actor that actually checks ChangeScene in a layer above those two actors.

The next is called Danger Room. It's quite the opposite. It's dark, bloody, and over the top. The gameplay is similar to red bit escape with a big difference being you don't need to have your finger o

(Quote)

F1 Cars: Top Down, Five Colours

(Quote)

2. In actor 1, if overlaps or collides with actor 2, destroy. Spawn actor 3.

Since this post was original flagged as spam, I gonna bring it to the top of the discussions once more with this comment so it has a chance to actually get seen. (Image)

On my iphone, every single time I hit the back button after reading a thread....not only does it not show me where I just was....it goes straight back to the top so I have to scroll to where I was at.

I'm right there with you. and on top of that, every time I publish an app, it logs me out of the forums.

I want my hero to jump on a platform which is actually an image. The platform is moving along with the background and physics are set to 0 in all cases for the platform. However, when the hero jum

@iKandy‌ https://auth.gamesalad.com/account/settings at the top. Pro Membership | Expires year-month-day

Hi Guys. I currently have an object falling from the top of the screen and I want it to be random so the behaviour I've used is Change Attribute: self.Position.X to random(8,560).

the destroy behavior was first, I moved it to the bottom but the problem persists.

First of all, make sure that the change attribute behavior is above/before the destroy actor behavior. When you destroy an actor, it ceases running its rules. So if the actor is being destroyed imme

It doesn't matter where the actor is in the layers if you have something like a game boolean let's call it destroy...if you change it to true and have if game.destroy=true destroy it should still dest

I am not sure how your whole project works or is set up but off the top of my head I would have the boss HP as an attribute in the boss actor itself and not as a game attribute.

So could this mean an actor on a level closer to the bottom would be unaware of an attribute change by a actor closer to the top? This would make sense in my circumstance.

I would say that this would be the problem. It's because you are telling it that when boss HP = 0 to destroy the actor and since it is never reset it is always 0 so when it spawns the next set of boss

Gamesalad reads from the bottom up so the last actor in the last layer will be read first.

I have an actor that spawn other actors. When a certain condition becomes true those actors destroy themselves. If I place the spawning actor below a certain level in the scene the spawned actors wi