One suggestion is to spawn a new dragon actor when the collision happens and destroy the existing dragon. The new dragon actor should have its own rules (e.g. no movement, no scoring, just animation

I had to deal with the timer behavior in the "Spawner Actor" for the following reason:

changed to false' rule. That way you could spawn the flying actor, not let go of the button, be moving left, and only stop/slow down/do something else if the button is released or something else cha

button. When jump is pressed, the walking actor spawns the flying actor and destroys itself. Now... when left is held down through the destroy and spawn, the spawned actor does not continue moving le

To make the obstacles appear more ''drastically'' I suppose you could have a game attribute. (Let's call it game.attribute A.) The scene has a height of 1000. A starts at 0. In the spawn actor rules l

I would I like to get a more drastic random Y position so the obstacles don’t spawn with say 50 pixels of the previous Y position.

Well the potential of invisible actors mixed with self.atrributes is quite powerful and can accomplish this. For example, say in actor 1 spawn invisible actor B on actor 2's position. (X,Y.) And in ac

That should spawn an actor every two seconds. But I suspect your issue is with actor positions... not timers. And unfortunately, I don't have time to sort through why that's not working.

I rarely use loops; most of the actors are in-scene thus I doubt it's a spawning issue; I do use quite a bit of animation; however, these problems aren't occurring when previewing or working on any sp

It seems you have a bottleneck (i.e. something causing a slowdown). Do you have any loops in your project, or an excessive amount of spawn actor behaviors? Or a ton of animation?

The actor's self.Time attribute continually increases. It doesn't stop or reset and it's not possible to force it to do so. The Timer behavior fires every x seconds depending on what you specify. I

Below is the spawner actor object and the actor to be spawned properties. Is there anything there that I am missing?

Ok, so my questions is this, is the timer reset after the objects spawns so that it can repeat the timer function prior to spawning another object and will the destroy call negate the timer or will it

     Spawn actor

I got the actor multiple spawn issue sorted out.

(optional step here if you want to spawn an actor before starting the intervals.)

a prototype. Unlocked instance actors will have unique rules and it may be that that's what happened.

why is it that when I set a spawn timer, it automatically spawns multiple actors of the same type? AM I missing something here?

And this by @Armelline: http://gshelper.com/product/spawn-time-changer/

Inhave my timers set up for each actor but what happens is the objects seem to spawn based on the first spawn instance of the actor and not from the spawn of each individual actor.