[MMORPG Game Development Series with C# and Unity] Part3: Unity Engine

Teacher, you can't go out anyway because of Corona, so please give me the next lecture quickly. I feel dizzy.

Personally, it was not an easy lecture. The editor part is intuitively understandable without much understanding, but the problem is that when a design pattern appears, it is the part where the manager is built, and it is hard to follow the flow of what it really means. However, after watching the lecture once and watching it again, I gradually see the intention behind building this framework, and I start to understand it. That's when I realized the true meaning of this lecture.. I really recommend this lecture. People like me who don't have much coding experience will probably have a hard time at first, but if you watch it several times and try your best, I think you will get good results! Oh, and the instructor often refactors to make the code as efficient as possible while giving the lecture, so you may get dizzy here, but since it contains a lot of know-how, I think it will be more helpful if you stop slowly, follow along, and understand it.

I think it's a really good lecture. However, since the game system is created with the game's scale in mind, it felt difficult for me who was new to it.

It seems to be a very high-quality lecture among the lectures I took while studying development. However, if you are completely new to Unity or are not majoring in this field, it may be difficult. Personally, I think it would be much more helpful to take this lecture after getting used to Unity by listening to simple game development books or lectures, and then learning the overall development flow and code patterns.

It was good to be able to learn about parts that I used to use without knowing the principles because I was in a hurry to produce while working in the field. And rather than uploading a framework like this lecture, I often thought about how to increase reusability and manage the system more efficiently by structuring it, as I was using code that worked at that time. This lecture was really helpful. And it was a great help in thinking a lot about the direction of coding to some extent.

It took me 8 months to finish the course I started taking in May. Unlike other instant game courses, this course has solid theory and structure. If I could learn game production with this level of quality, I would have taken it even if it was 1 million won, not 80,000 won. Also, I am so grateful to the instructor who actively helps me with questions and answers. I am learning a lot ^^

Rather than trying to understand everything after listening to it once, it seems best to quickly watch it first and review the parts you don't remember. To be honest, if it's your first time using Unity, it's a bit difficult to understand everything at once. If you think that you'll have a portfolio if you finish it, rather than listening to it, think that you'll be able to draw a picture of yourself making your own portfolio if you finish it.

I have been interested in development in the design field and have been working since I took Rookie's lecture and got a job 3 months ago (as a Unity developer). It was difficult for a non-major to understand it after listening to it for the first time, but I listened to it 2-3 times and Googled the parts I didn't know to gain knowledge and got a job under the conditions I wanted. I still have some shortcomings in C# and Unity, so I plan to listen to it at least 3 more times and also take C++ and Unreal lectures. I recommend Rookie's lecture to those who are studying for fun, even if they are not working as developers!