@toastyee Just played and I have the top score. (Image)

The destroy after 5 seconds rule can go anywhere... it doesn't really matter because it's not ordered (it doesn't have to check the time either before or after something else happens). It would look

If I want to destroy this actor is it is not touched should I put that rule after or before the rule i just sent to you. Basically, after 5 seconds, destroy actor.

As a rule, I never destroy an actor and then place rules or behaviors after the destroy behavior. I always put the destroy behavior at the end/bottom of the rule.

Hmmm ok...maybe place a timer and imbed the rules of the bullets...use the "for" attribute. Give the bullet some time to move across the screen before you destroy it...should it not

What players need to do is tap on the virus, which appear on your devices to destroy them before they break your phone.

Spawn actor in relation to one another?? Not really random and it would be obvious how everything is in order. No overlap and not close to each other. This is endless runner where objects move towards

I'd make 2 actors for your portals, then when you collide with one, destroy that actor, and have the other portal spawn it after [time], but with an offset so it doesn't overlap the portal it's coming

And if it "can't" what are the workarounds? Off the top of my head I'm thinking I could plan out what objects are on the screen as the character goes up or along the screen. After sp

Does a destroy behavior on the actor that I am spawning effect my table in anyway? Example, if I destroy an actor will it appear right away (which i dont want) or will it know to wait until the game i

You are getting pretty close. something like that but the clouds would be spawning only at the top of the screen to not fill the screen too mutch. Just like in picture nr. 2. Character goes up - cloud

center the camera again over the cannon, then destroy actor on overlap with cannon. this could solve the issue.

Thanks for the help, although it hasn't fixed the problem, it still occurs even when i made a Boolean for the collision and if true, destroy. i just do not know why

Why does the actor has to be spawned back to position if it is a large scene? Do you replicate and destroy those spawners or how? I just can't find an answer (Image)

I have this idea of an app where the player's city is written on the top of the screen

* Fixed creator crashing when moving an actor from one layer to another.

Here's a demo that picks a random number from a table. You can assign the number (game.randomNum) to a spawned actor by spawning the actor right after game.randomNum is given a value. In the spawned

When a spawner hits a detector, it can replicate itself above the other spawners wherever you want it, then destroy itself.

having the object you are controlling at the top of the screen with the controls at the bottom could be a little disconnected.

(Quote)