Search code examples
unity-game-enginecoding-style

C# used for Unity scripting, best practice about scope of variables

I just started learning Unity, but I work as a software developer. Generally, in programming, it is a good practice to make variables private if that is possible.

But in Unity tutorial (made by unity) it is suggested to make variables scope public so you can change it on the go (the one that is useful to adjust as you go in Unity for testing).

Is it a good idea/Unity practice to make variables public, or should I stick to making them private?

Solution

  • Use the style that you are comfortable using. If you still want to have the variable show up in the inspector use the following attribute: [SerializedField]

    This should allow you to program the way you want along with having the functionality of the Unity inspector.