Course Reflection
Thanks to the opportunity in this course, I was able to design two games and a board game. The most interesting thing about this course is to see various ideas from our classmates developed into real games. I had a chance to be the artist of the game design for the first digital game prototype and the developer for the final project. There are definitely things very different between these two roles. I felt more stressful being a developer as it was my first time coding with C#. However, the process of solving problems and managing time taught me a lot because as a developer I learned to prepare more time in coding than my prediction and quickly spot similar coding problems online and look for answers. The book and lectures of the course changed my mind about designing a game. I used to believe that game designer should follow their own preference and interest to make games. However, what’s important to make a good game is to know the interest of the majority. I also love the definition I learned in this course about game, especially the phrase “unnecessary challenges”.
Most of the games I played before are single games. However, in this course, I not only got to play party games but also make games with other group members. We wrote design documents, distributed works, negotiated about personal preference for the game, complained about each other, and finally became friends. The process was stressful and but convivial. I appreciated that all my teammates are honest and listen to opinions. Overall, I think the course is designed pretty well as a beginner game design class.