Question Trying to access childrens variables from parent

I’m instantiating gameobjects that on creation gets a random variable by their own void start script in their prefab. I now want that variable collected in 1 list in order to make a graph using them later.

My problem is now that I have no idea how to access these variables from a parent. Is there any way I can do this?

 

When spawning the child, add the component on the spawned child to a list on the parent. Then you have a list of all the components.

There are many methods to do this (kurt might reply with a list as well haha)

 

Get the parent of all the parent objects:

child.transform.root

to get the top most object in heirarchy.

Or just next parent:

transform.parent

Or from parent to children:

Code (CSharp):

1. body_obj = transform.Find("body").gameObject;
2. rig = body_obj.transform.Find("metarig").gameObject;
3. root_bone = rig.transform.Find("spine").gameObject;

But in order to get the script after getting the gameObject:

ScriptName script1 = obj.GetComponent<ScriptName>();

 

I do not recommend using .Find
Stuff like GetComponentInParent or GetComponent(s)InChildren is less error prone.
Setting everything when spawning is a lot cleaner and more SOLID

 

As far as gameObject.Find(), I totally agree. But when going through a massive hierarchy, like a bone rig from a blender model, as far as I know, there is no better way to get said bone. Like "R.indexfinger.001" or even "spine.007".

For example:

Code (CSharp):

1. spine3 = transform.Find("body/metarig/spine/spine.001/spine.002/spine.003").gameObject;

Is perfectly fine since it goes through the hierarchy of transform.

 

Referencing variables, fields, methods (anything non-static) in other script instances:

https://forum.unity.com/threads/hel...-vars-in-another-script.1076825/#post-6944639

https://forum.unity.com/threads/accessing-a-gameobject-in-different-scene.1103239/

It isn't always the best idea for everything to access everything else all over the place. For instance, it is BAD for the player to reach into an enemy and reduce his health.

Instead there should be a function you call on the enemy to reduce his health. All the same rules apply for the above steps: the function must be public AND you need a reference to the class instance.

That way the enemy (and only the enemy) has code to reduce his health and simultaneously do anything else, such as kill him or make him reel from the impact, and all that code is centralized in one place.

This can help you keep things tidy when you're instantiating stuff:

Factory Pattern in lieu of AddComponent (for timing and dependency correctness):

https://gist.github.com/kurtdekker/5dbd1d30890c3905adddf4e7ba2b8580