Скачать или смотреть Understanding Inheritance in Unity C# : Clarifying Confusion

This guide explores common issues with inheritance in Unity C# , focusing on resolving the confusion surrounding GameObjects and their behaviors.
---
This video is based on the question https://stackoverflow.com/q/68157117/ asked by the user 'Egor' ( https://stackoverflow.com/u/16311465/ ) and on the answer https://stackoverflow.com/a/68157390/ provided by the user 'CorrieJanse' ( https://stackoverflow.com/u/15119845/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: I am confused with Unity c# inheritance

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding Inheritance in Unity C# : Clarifying Confusion

When working with Unity and C# , many developers encounter confusion regarding inheritance, particularly when two scripts interact with the same GameObject. If you've found yourself puzzled by why your Parent and Child scripts behave unexpectedly, you’re not alone. Let's dive into the details to clarify this issue and provide a solution.

The Problem: Confusion in Script Behavior

In the scenario presented, you have two scripts:

Parent

Child (which inherits from Parent)

Both of these scripts are attached to the same GameObject named enemy. The enemy tries to find another GameObject named Hero, but inconsistencies arise in the output logs, where hero is Null in the Parent script's Update() method, even though it successfully logs in the Child script.

The Core of the Issue

The heart of the confusion lies in how the Child script accesses the members (like the hero GameObject) of the Parent script:

Instantiation Misunderstanding: It may seem like the Child script should be accessing the hero GameObject defined in the Parent script. However, the Child script effectively creates its own instance of hero. This is a common misconception when dealing with inheritance in Unity.

Function Calls and Scope: The Parent script's FindHero() function is never actually called from the Parent script itself. Each script operates within its own scope, and unless specifically called, methods in the Parent are not executed.

The Solution: Simplifying Your Approach

To resolve these issues, consider the following suggestions:

Steps to Fix the Problem

Remove Redundancy:

Since you have both Parent and Child attached to the same GameObject, this can cause confusion. It's best practice to only attach the Child script to the GameObject when it inherits from Parent.

Call FindHero() in the Parent Update:

To ensure the hero GameObject is found and managed consistently, you could call FindHero() in the Update method of the Parent script:

[[See Video to Reveal this Text or Code Snippet]]

Testing Only the Child Script:

After applying the above changes, only use the Child script on the GameObject:

With everything in one place, the child inherits all necessary behavior while accessing FindHero(), ensuring that hero is always up to date.

Conclusion: Simplified Inheritance

When working within Unity, remember that inheritance means that the Child script extends from the Parent script, but each maintains its own state unless its methods are called. Avoid redundancies by not attaching both scripts to the same GameObject.

By following these steps, you can clarify confusion and ensure your inheritance structure in Unity functions correctly. Happy coding!