Avoiding a race condition with instantiate?

I have a n object which does stuff when it's created, in Start()
I would like it to sometimes (not always) not do that stuff, when instantiated from a certain area of code.


So my question is, in the part of code where i'm instantiating the object, can i reliably set a variable to some value on the next line, to tell it not to do its usual startup procedure?

Does the object call Start() immediately when its created, or when the current code finishes, or the next frame, or what?

 

Start is called before the first frame of updates.

In practical terms this means you can rely in any data set in the lines of code immediately following Instantiate.

Awake has the opposite behaviour, and will run as part of Instantiate.

 

I found an awesome image that explains it all. If you google for unitylifetime.png you will see all the different variants that people have made, including a flowchart-y one and a circular one. It clarified a lot for me.

 

Ya its also in the docs
http://docs.unity3d.com/Manual/ExecutionOrder.html

 

wow, that is impressively helpful

thanks guys ^^

 

Yep, use Awake for anything you need to have absolutely immediate access to...