I’m using Unity 5.1. These component fields were removed from MonoBehaviour, right? Indeed, if I remove the fields, I get an error about how they are gone and the automatic script updating tries to kick in. Sure, I can add the “new” keyword to suppress the warnings, but I’m confused why that should be necessary if those fields were removed. What’s going on?
The formerly-deprecated fields are now marked as obsolete. That means they are still in the base class definition and hence will trigger the error if you attempt to use them, or in your case the warning if you hide them with a same-named field in a subclass.