Can't use variable from another scrip

Unity Engine
,
1

From this class i am trying to get the “isActive” variable into my other script;

using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class [B]NPC_interact_text[/B] : MonoBehaviour
{
    [SerializeField]
    GameObject text;

    public bool isActive;

    void awake()
    {
        isActive = false;
    }

    void OnTriggerEnter2D (Collider2D collider)
    {
        if (collider.gameObject.CompareTag("Player"))
        {
            text.SetActive(true);
            [B]isActive[/B] = __true__;
        }
    }

    void OnTriggerExit2D (Collider2D collider)
    {
        if (collider.gameObject.CompareTag("Player"))
        {
            text.SetActive(false);
            [B]isActive[/B] = __false__;
        }
    }
}

And for some reason it gives me this error,
on this line

using System.Collections;
using System.Collections.Generic;
using UnityEngine;


public class [B]NPC_text_follow_player[/B] : MonoBehaviour
{

    public GameObject thisObj;

    NPC_interact_text check;

    void start()
    {
        check = thisObj.GetComponent<NPC_interact_text>();
    }


    void Update()
    {
        if (check.[B]isActive[/B] == true)
        {
            Debug.Log("yes");
        }
    }
}

What can i do?
And sorry for any wierd code,im fairly new to coding.

2

Probably because you have start() instead of Start() and awake() instead of Awake()
Capitalisation matters in C#. If you are trying to use methods that are built-in to Unity, then you need to spell (and capitalise) them correctly, otherwise Unity will assume that these are your own methods that you will deal with.
Because your Start method is named wrong, then you never get a value into your check variable so that is why you get that error on that script.

3

Almost certainly correctly diagnosed by BaBiA as simple typo errors.

If you plan to monkey-hammer-bang tutorial code in, keep this in mind to save yourself a LOT of time and endless frustration:

How to do tutorials properly:

Tutorials are a GREAT idea. Tutorials should be used this way:

Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That’s how software engineering works. Every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly. Fortunately this is the easiest part to get right.

Be a robot. Don’t make any mistakes. BE PERFECT IN EVERYTHING YOU DO HERE.

If you get any errors, learn how to read the error code and fix it. Google is your friend here. Do NOT continue until you fix the error. The error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost.

Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there’s an error, you will NEVER be the first guy to find it.

Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!

Also, this will ALWAYS fix null references:

The answer is always the same… ALWAYS. It is the single most common error ever.

Don’t waste your life spinning around and round on this error. Instead, learn how to fix it fast… it’s EASY!!

Some notes on how to fix a NullReferenceException error in Unity3D

  • also known as: Unassigned Reference Exception
  • also known as: Missing Reference Exception
  • also known as: Object reference not set to an instance of an object

http://plbm.com/?p=221

The basic steps outlined above are:

  • Identify what is null
  • Identify why it is null
  • Fix that.

Expect to see this error a LOT. It’s easily the most common thing to do when working. Learn how to fix it rapidly. It’s easy. See the above link for more tips.

You need to figure out HOW that variable is supposed to get its initial value. There are many ways in Unity. In order of likelihood, it might be ONE of the following:

  • drag it in using the inspector
  • code inside this script initializes it
  • some OTHER external code initializes it
  • ? something else?

This is the kind of mindset and thinking process you need to bring to this problem:

https://discussions.unity.com/t/814091/4

Step by step, break it down, find the problem.

Here is a clean analogy of the actual underlying problem of a null reference exception:

https://discussions.unity.com/t/840647/7