Non-private members and methods create multiple fields/buttons in derived classes' inspectors

[PJBarczyk]

When a script derives from another MonoBehaviour script, all non-private members and methods (public or protected with SerializeFieldAttribute) create extra fields or buttons.

Example

Create the following scripts in your project and add them to a GameObject:

// file: A.cs
public class A : MonoBehaviour
{
    public int aPublic;
    [SerializeField] protected int aProtected;
    [SerializeField] private int aPrivate;

    [Button] public void TestA() => Debug.Log($"Test from {nameof(A)}");
}

// file: B.cs
public class B : A
{
    public string bPublic;
    [SerializeField] protected string bProtected;
    [SerializeField] private string bPrivate;

    [Button] public void TestB() => Debug.Log($"Test from {nameof(B)}");
}

// file: C.cs
public class C : B
{
    public int cPublic;
    [SerializeField] protected int cProtected;
    [SerializeField] private int cPrivate;

    [Button] public void TestC() => Debug.Log($"Test from {nameof(C)}");
}

The inspector will look like this:

Related issues

The seems related to #12, though it covers an issue happening with private members too.