YES I HAVE BEEN LOOKING FOR THE ANSWER TO THIS FOREVER!!!! What is the other attribute and more rules... I am trying to spawn randomly 16 actors but everytime it spawns the same actor twice it doesn't

I haven't played it, but I'm imagining what you could do... you want to spawn a trail of dots... so why not associate the dots with an attribute. When the bird gets hit, it could trigger the old dots

Thanks. I was thinking that I could use modulus to cycle between two values. Then have the cycle triggered when the projectile lands. then in the trajectory markers have a rule that destroys them on e

Spawn actor 'Wall'

I've got the sling shot down perfectly (well as good as it needs to be), but I want to have the little smoke puffs that spawn as you fly through the air. That is easy to do of course, but what I can't

Interesting last bit! Do you have an example of how to use unique actor ID and a counter to keep track of attributes?

Having each with a unique actor ID can aid in selecting from a bunch with game counter to keep track or a set of attributes to keep track of their state.

So it seems that Spawn Actor takes a lot of CPU time. If I am to create my actors by hand and hide them on the scene, what would be the best way to pick one that is currently not used?

Unique Game PlayDraw lasers with your finger to bounce Johnny around the solar system. Plan your moves to collect the stars using the least amount of lasers. This unique puzzle / platformer will have

Haha, that's a good one scitunes! Unique.

In the enemy actor add a "spawn actor" behavior (you'll probably want to put this in a timer or other sort of condition to determine how frequent the enemy fires.)

I have to say, I love the "doodle" sketches for these games! It makes it very unique! Keep up the good work and lets keep the GS apps in the top 100!

I searched but can't seem to find a post I saw on having actors off screen and call them into position (like a spawn) instead of using spawn - this is supposed to be better for rule heavy actors corre

IT'S A UNIQUE OPPORTUNITY, BUT NOW!!!

You would think the otherwise behavior in the first rule (separate from the spawn/destroy rule) would force to false. I can't see anything in the entire script window that would cause an override. A

Yeah, I took a brief look at it the other day. In the one Rule set, you have a Change Attribute, a Spawn Actor, and a Destroy Actor behavior "loose" inside that Rule.

-- spawn R

you have to use attributes and random numbers and based on the random number you must spawn your "patterns".

I had a similar thing going on with my game Food Fight!. I have an actor that jumps and when you push a button, he throws (spawns) a pot. I think I may have tried what you did, and had similar problem

spawner, when game.firebutton = 1, spawn actor (missile),