(Quote)

You got a yes GS can handle it answer from one if the top devs here on the forums. Why in earth are you rejecting the answer? What hasn't been answered for you?

I got a snapchat from one of my friends and was alerted through the top of my screen as a notification.

Why do you have two destroy rules with the same conditions in that shot? Usually lag is a result of bloated code. As you learn GS you will understand logic trees better and be able to refine and slim

@Hopscotch Yes, each laser has a constrain that subtracts from the Princess's location, so that if they exceed a set distance, they destroy themselves, for example, some destroy themeselves after a ra

Thanks Hopscotch, sorting the layer order did the trick, thanks!

1- that demo is great still it starts spawning a little bellow the top of the screen, how can i make it spawn from the top.

So imagine that i have 6 random spawners on top of my screen, and i manage to make them randomly spawn, but i want one of the spawners and only one to spawn nothing randomly, how can i do this?

Hi Guys. I have a intro graphic that overlays the game, and when it is clicked it is destroyed. The problem is when I click it I sometimes accidentally click actors beneath it.

actor they will have their own rule to when to destroy .. i think having this properties will be very useful to kill different actors with simple one rule save lot of time .. like for example when u

So basically, once a book(actor) has been made true or false, once it's been destroyed or moved on, it can be made 0 (zero); (if a book "fails" you can call it 1, a true book, 2).

Ok, So here is what the early frame looks like. The grass moves and the books move from off stage on stage and stop in front of buddy.

It could work if it was a case of "destroy all instances of this actor". Would be less helpful, but helpful nonetheless. To be honest, though, there are 1,000,000 things I would like

(Quote)

You do realize that your drop-down menu would have to contain every instance of every actor on the scene? So if you had an actor called enemy and had ten copies that had spawned, you'd have &quot

Hey GS team .. any chance you may consider adding a rule to destroy actors that works the same way when spawning them .( like you have drop down menu to chose which actor to kill ) this way we can use

Yes, the code is read from top to bottom, but it's done in a fraction of a second - i.e. it doesn't wait until the first piece of code is completed before moving onto the next.

I assumed once an actor is spawned the code is read from top to bottom. I have no triggers.

Instead of respawning and destroying the actors I would change their positions or change their Attribute number so they become a new number. I would do this by storing 3 or 4 patterns in a table and p

Thanks! I really appreciate your help. I'm still new to GS, so it took me a while to wrap my head around your demo, but it's quite genius. Only problem is, the letters at the bottom should be spawned