Skip to main content

Towards a Minimalist Design

    As a budding game designer, I have very limited resources available to me when developing a game, either this be time or the amount of work one person can accomplish on their own. One of the design philosophies that people like me can follow is one of minimalism. After reading the scholarly article Towards Minimalist Game Design I have had some ideas on how to make my games more tangible for one developer to create.
    An important observation is in minimalist games that are made by indie developers and can claim wide success. One such game is Undertale, created almost entirely by one developer Toby Fox. This game expresses many of the minimalist design philosophies that are described in the scholarly article, which is the focus of this post. Most primarily, we see the lack of macro-mechanics. This is a primary target when designing a minimalist game as it simplifies development while not necessarily sacrificing depth of play or exploration. The main macro-mechanic that exists in undertale is to not allow your hit points to reach zero. This is underlined by many micro-mechanics that all work together really well. From the simple movement system, working seamlessly with the simple graphical approach; to the more complex system of attempting to befriend a creature rather than killing it. By selecting one maco-mechanic, Toby Fox greatly simplified the complexity present in many RPGs in present memory. Permitting him to create an RPG, without building complex damage tables like the one shown in this article.
    In developing my current 2D game project, I will have to keep these ideas and goals in mind in order to create a game that is both intriguing and deep, while not being overly complicated to build and maintain.
Image Source: Unity Form

Comments

Popular posts from this blog

The Art of Game Design: Chapters 6 and 7

    The Art of Game Design  continues to be an intriguing read that surprises me in new ways with each chapter. Chapter 6 focuses on the importance that theme has on games and how theme should be treated in a game's design. Theme isn't just something that the player learns from the game, it is the thought or idea that the game should try to represent in every possible way it can. This chapter covers two forms of themes, experienced and resonant themes. Experienced themes are just that, the themes that are experienced by the player through the game's story and setting, however resonant themes are a bit different. Resonant themes are the ones that are below the surface and aren't really experienced but have some deep truth that parallels those truths that the player holds. These are the themes that resonate deeply with players and make a story truly meaningful to a player's core.      To people who do not really play video games, they can be easily seen as a...

Magazine Columns - Backbone of Every Good Layout Response

There are many aspects that must be considered when designing a magazine. The content is very important, but one aspect of the design that no one really thinks about is the layout of the magazine. The grid is how images and text are placed around the page. It can determine the size of objects and how much white space is between each element on the page.  Most text in magazines appears to be set out into 3 columns. However, one of the most common layouts utilizes 12 columns in order to appear to have 3 columns. This gives much more layout control over what is shown and how it is shown. Its very surprising that a 12 column layout results in 3 columns of main text. However, the goal of this is so that it is modular. In computer science, one of the most important things that you consider when coding is to try and make your code modular. When you can use the same layout on every page, it means that it is dynamic and interesting since each page will feel like it follows the same rules. T...

The Art of Game Design: Chapter 8 and 9

    Chapter 8 in the book The Art of Game Design  is all about the actual production process that is followed after brainstorming is complete and a team has an idea for what game they will be developing. One of the topics that this chapter focuses on are the ideas of software development, waterfall and a more circular idea designed by Barry Boehm. As a computer science major, I have encountered both of these ideas through my time in college and in the busniss world. Both theories have their positives and negatives, but the idea of "waterfall development" is a much stricter way of approaching software development when compared to Boehm's approach.     With a waterfall approach, this does not leave any room to go back and revisit the original idea and add or remove core features. This approach was used in the development of many old forms of windows, which also coincided with how the software was sold. For example, Microsoft's windows operating systems. Win...