Maybe a stupid question

Script B (attached to many objects) references Script A (just one exists, attached to Object A). Object A is not often active in hierarchy, so when Script B tries to Find Object A with tag in the Awake() function, it often fails due to Object A's active status.

I thought about making a function like

Code (CSharp):

1.     void FindObjectA()
2.     {
3.         objectA = GameObject.FindGameObjectWithTag("A");
4.     }

that is called every time I need to reference it

Code (CSharp):

1.         if (objectA != null)
2.             FindObjectA();

But that seems like a REALLY BAD solution.

Assigning the gameobject in the inspector is not an option.

 

Lookup the singleton pattern

 

I haven't used a singleton in a long time. I heard it was bad practice.

 

No it's Not. Finding gameobject by tag is

 

It is not a bad practice to use singletons. It is just some people abusing it.

 

Yeah, just do it in a sane manner, you can use everything in a wrong way.

I never had a real probkem with them.

 

Find Object by tag is bad practice? What about transform.Find() for children? What should I do instead when I need to find Object(s) in my scene Hierarchy?

 

Just cache objects into some collection.

 

Its fine if its one call every now and then, but I personally only use them on load screens.

 

Right now I'm declaring variables and only using those Find functions on Awake at the start of the scene, then referencing the variable to execute the code

For example:

Code (CSharp):

1.    
2. NewTimerScript myTimer;
3.  
4. void Awake()
5. {
6.         myTimer = transform.Find("Timer Holder").GetComponent<NewTimerScript>();
7. }
8.  
9. void OtherFunctionsInThisScriptThatReferenceTheTimer()
10. {
11.        myTimer.ThanksForYourHelpGuys(iReally, appreciate, it);
12. }
13.  

Is this a bad way of going about this?

 

Then its fine, they are a problem when calling them during gameplay