The more I learn about C#, the more bad habits I see in Unity tutorials. Things like using cascading if-else statements, single char strings to perform Boolean logic... It is far, far better to learn C# first and come back to Unity after. Once you can make multi-threaded WPF apps that link to a database, I would start looking at catlikecoding.com /unity/tutorials/ Some of the best tutorials I have seen. It really dives into some advanced Unity topics like procedural mesh manipulation. Best part is there is none of that "intro to C#" stuff like "here is an int. It's a number!". He also has some remarkably good programming habits.
The more I learn about C#, the more bad habits I see in Unity tutorials. Things like using cascading if-else statements, single char strings to perform Boolean logic... It is far, far better to learn C# first and come back to Unity after. Once you can make multi-threaded WPF apps that link to a database, I would start looking at catlikecoding.com /unity/tutorials/ Some of the best tutorials I have seen. It really dives into some advanced Unity topics like procedural mesh manipulation. Best part is there is none of that "intro to C#" stuff like "here is an int. It's a number!". He also has some remarkably good programming habits.