If Attribute Select equals 2 then destroy this actor, and spawn actor Worker on the exact same position.

Yeah, agreed, it does seem a little counterintuitive, but the logic is sound. There are other ways to speed up spawning multiple actors, just did a quick test and was able to spawn 720 actors in just

----Spawn something at A

...and unfortunately, since I started 8 months ago, with my catchy li'l title, there have been numerous "Flap" and "Cat" combination titled games... (I actually thi

which correspond to the pattern of enemies spawning cant just stop when all the rows have been deleted. So, once the rows are deleted, I used Copy Table to restore the table . However, there is nothi

@Alchimia Studios‌ Okay so what I did is put every 0 seconds change attribute self.spawned to true (I want a continuous stream.) & I don't understand what you mean by "Also shouldn't

that is my main actor (not the thing I want to spawn). The red is my background.

However, if you think you have an original concept, it also becomes important to care for this idea, that this remains unique and original at least until the time of publishing.

You would need to decrease the time it takes to spawn for the gaps to be closer.

You'd have to adjust the spawn frequency based on the actor's speed.

My Actor1 gets spawned every 1.5 seconds.

And yes, there's no reason to need to change the random value in a separate actor. Just use random(-100,147) in the x position field of the Spawn Actor behavior.

Every 2 Secondsspawn actorfrom position random (x,x), y

That logic is incorrect. You are changing the self.spawned to true before the actual spawn occurs in a ruleset reliant on the self.spawned being set to false in order to trigger.

Ok, here it is. Click on the actor that says Spawn on the top right to spawn instances of the falling actor.

No. What you're describing is not typical behavior. When you spawn an actor, it should always take on the prototype rules and attribute values. Can you describe how you verified this? Are you usin

Yes. Now can you explain a bit more...? For example, do you want a single attribute to have different values in several instances or do you want a bunch of separate attributes? And do you need the

There's not really a need to "load the new value" or "[trigger] an action" though I think I get what you're saying. The main issue is that there is no spawn behavi

* Where is the Spawn Actor behavior?

So intend of spawning at . . .