where to initialize static classes?

Got a few static classes with no state or dependencies that are very useful to call from anywhere. What's the best way to call their Initialize() functions at game start?

 

I always have a GameControl Monobehaviour attached either to a main camera or a dummy GameObject (usually called Game). Most initializations would run from the Start method of that Monobehavior. There are other ways to do it I guess. But that is the one I use.

 

Ahh ok thanks cdevl. Was thinking it would require a game object.

 

Just make sure that if that GameControl GameObject doesn't do any updates (mine actually does; it controls global actions - like Pause) - delete the Update method from your code so Unity doesn't call it each frame. I actually asked that question here on the forum. If you get rid of an Update method then there is no per-frame overhead.

 

You may also make sure that if you are loading a new scene and destroying GameControl that you don't reinit your statics (or just make sure that your init(s) are re-enterable).

 

It does not require a GameObject.

For what you describe (no state, no dependencies, just provides functions) making the functions themselves static sounds like it would suit best.

 

a static constructor is guaranteed to (implicetly, no need to call explicitely) run before any access to the static parts of a class. so call initialize there.

if other gameobjects rely on the data in your class this can cause problems when you don't consider script execution order.