Nov 6th, 2008

Making a game about making games, projects

In a previous post I explained what motivated me to make the game I am currently making as my final project in college. In this entry I will actually describe what I have achieved so far, and my plans for what’s to come. If you so wish, you may play the game, incomplete as it is, before reading what follows. If you do, I’d be very interested in hearing about your experience, how you approached the game without knowing exactly what it was about, what could have been clearer or better.

What I sought, as I explained in that other post, was to create a game whose main objective is not to rack up points, but to create a visual composition. This is a game about creativity, indeed; a subset of games that, I have found, is not very largely represented.¹ Kenichi Nishi said something in an interview that I quote here because I consider to be extremely significant:

Recently, games have been ‘passively interactive.’ Users do not really have to think about what to do; they are guided around until they reach the end of the level. These types of games do not rely on the creativity of the users.

This is why I started to consider my idea more important than at first. Although there have been games like Mario Paint, that are like tools that are given a context of fun, I wanted to make something simpler, something abstract and more concentrated. There was also the question about how this would work as a game; I didn’t want it to become a color-matching, chain-making fest, so how to evaluate what was being made for its own sake? It didn’t need to be competitive, but it also needed a purpose, a raison d’être. There was the possibility of it being multiplayer, and people judging each-others compositions, much like the abovementioned Nishi’s own game, Archime-DS (or LOL, as it’s being brought over to this half of the world). I took a bit of that idea, as I will explain later, but I deliberated some more until I came to the conclusion that the best would be not to judge quality, but to evaluate compositive characteristics, or parameters, as I’ve grown used to calling them. The point being that every visual composition can be evaluated in terms of different characteristics, like how symmetric it is, whether it uses warm or cool colors, whether it is rhythmic or not (presence of visual patterns), etc. We can use these parameters to objectively determine if a composition is harmonic and pleasing to the eye, if it is foreboding, if it is unsettling, etc.

Personally, I am more of a supporter of holistic rather than reductionist approaches to analysis, but in this particular case (and in many others) it is much simpler to compartmentalize the data—especially given that I am hardly a mathematician, or even a programmer, so it simply made my work a lot easier. I realize that to this point I’m still talking abstractly, so let me show you the game proper.

That is what it currently looks like. In the center, but leaning toward the top and left, is the canvas: a grid where the player creates his composition. To the right is the carousel; sort of a conveyor belt of colored groups of circles, that the player can grab at any time and drop on the canvas. In a bar at the bottom there are a series of pictograms of differing sizes: they are actually dynamic, and change depending on the current characteristics of the composition, as perceived by the game (right now the algorithms that calculate this are not very finely tuned). Each pictogram changes to either a neutral, high or low graphic depending on the value: For instance, the fire icon indicates that the colors are mostly warm, and it would change to a snowflake if it was the opposite. Its comparatively small size means that it is not leaning that much toward warmth. The pictograms still need some work for them to be easier to understand, since, as I said in that previous post of mine, this game will use no words, so they need to be self-sufficient. Finally, in the bottom right is the time counter, which, when depleted, will prompt the game to show a results screen, which is pictured below. (continue reading)

Oct 13th, 2008

Ambitions of pushing the envelope games, musings, projects

I’m currently in my final semester for the Bachelor of Graphic Design degree, so I’m devoting my time to a project I haven’t discussed here so far. Now that I have something to show, though, I think it’s time to talk about it a bit. I’ll start from the very beginning: the conception of the idea.

I’ve been an avid videogamer for the best part of my life, so I can account for many hours spent in front of a screen, with a controller in my hands. One day, around two years ago, probably while playing this brilliantly elegant game called Polarium,¹ I realized that I was having more fun creating levels, and making sure that they were both solvable and aesthetically attractive, rather than just playing the game proper. I found that the visual patterns created by the simple colored shapes in puzzle games like Tetris, Puyo Puyo and Puzzle Bobble could, and sometimes would, form beautiful patterns. This is, of course, where my training in design comes in; I realized that a game could be made where the objective, the very goal, was not to match shapes or make chains, but to create an interesting visual composition.

I had very little experience programming, though, so I never took it upon myself to make that game. Time passed, and one day there was a special event, hosted by a friend, called the Super Game Bakedown, that simply consisted of creating a game for the duration of a single month, in the spirit of the NaNoWriMo. I knew I couldn’t achieve such a feat, but I joined anyway, and made it my goal to finish a design document for this dream game of mine. I even added a secondary characteristic to the game, which was an idea that had intrigued me for a while: The game would not use words (or numbers) whatsoever. In the end, I didn’t even finish the design document, but I did get a clearer idea of what I wanted to, and could, achieve. (continue reading)