Persistent vs Action Behaviours

sketchling

I have been trying to figure out which behaviours will keep having an effect and which ones will only be called once. I made one actor create three others when it is destroyed and pass on its motion relative to an explosion which worked well, but then when I shot at another one of the same actors, or any of the children whos motion was effected, the motion was changed on all of them as if there was a constraint. I only used change attribute.

I even made a rule to check a 'justspawned' attribute, set up the initial motion and then change it to false... and even though the show text SHOWED me it was false, the change attribute rules inside it still altered everythings motion.

Is there any documentation that explains how these behaviours are processed? like what happens perpetually and what stuff doesnt. I find it very confusing and then it crashes. Luckily not much I did in the last hour could be counted under the heading 'progress'.

I love what this program can do...I just wish i understood what was actually happening!

SlickZero

Any rules that you apply to an actor will carry over into other instances of that actor unless you unlock the behaviors when it is on the stage, and manipulate the script. So those 3 actors are acting as one because i'm guessing the are the same actor?

You can either create multiple instances in the actor bin, or you can manipulate the script onstage by double clicking the actor and unlocking it's behavior window. But if they are spawned after a certain event, then you won't be able to, so you may have to create multiple instances of that same actor, and script accordingly. Here is a reference library that might be of some help to understanding what all the features do in GameSalad. And have you been to the youtube Cookbook page?

Reference library
http://gamesalad.com/wiki/reference_library

Cookbook page
http://www.youtube.com/user/GameSaladCookbook

sketchling

Thanks, thats helpful... I think its just getting the hang of what gamesalad is actually doing under the hood. Each spawed rock was individually being destroyed by the bullets etc etc, but I had an explosion that was changing a game attribute the spawned actors used to generate their initial velocity and must have been changing all of them. What I still dont understand is why a setting set once should remain linked without a constrain... Ill have a looksee, im probably doing something silly.

Ill give it a go tonight and see if I can fix it. Thanks for the help!