Hello, Quoting from beginning of the documentation on SerializeField: "You will almost never need this". From my (limited) experience, I can say that it is the standard way to make fields/variables editable and definable through Unity Editor, without making them public. Please enlighten me. Yet another section (starting statement) in that page states that SerializeField is used to "force Unity to serialize a private field", but I guess the purpose here is just to simplify things, as slightly down the page it says "... nonpublic nonstatic fields marked with the [SerializeField] attribute". Cheers, Sahin
There's some bad advice in the docs. This is an instance of this. It makes perfect sense to use SerializeField a bunch, unless you really want all of your serialized fields to be public.
Ow, I see. I thought perhaps there is a better way out there. It's just like StackOverflow, I guess, but without comments to warn you...