When agj.cl first went live, the only thing that was there was my old portfolio website, made in Flash. It was my first experience with actionscript, back in 2007. I took it down a while ago because it had grown too outdated, and since it was so hackishly conceived, I wasn’t planning on updating it. Well, I’ve finally made my new portfolio page. Things have changed enough that only two of the works I selected for it remain from the old Flash portfolio.
I’ve archived the older one (in Spanish) for posterity.
I had things to do and places to be Friday night and all Saturday, so only got started on my Ludum Dare entry by Saturday night. LD is a 48 hour competition in which I also participated four months ago; back then, I made Heart. This time, I didn’t get to make such a complete game. The theme was ‘caverns’, so I had planned to make a rhythmic game about flying through a cavern (okay, more like a tunnel) and avoiding obstacles to the beat. It was actually pretty hard to just get the visual effect right, so I got only as far as adding some randomized obstacles, and throwing in a sound effect upon hitting one. So, it’s far from a complete game. The code that would allow me to add in a music track and have it be synchronized to the images is already there, at least.
This one was made using FlashDevelop and Flex SDK 4, coded in actionscript 3. Below you can see all those hours of work, squashed into just a few seconds.
This latest TIGSource video game competition has a double theme: adult/educational. I have to say, it’s a fantastic combination. The idea was that entrants could create a game under one or both themes. I wish more entered games had used both simultaneously, but, well, not even I did that in the end.
During most of the duration of the competition, I didn’t find the time to make my game. Also, I was finding it hard to come up with an idea. Educational games are tough to make; they require familiarity with the taught subject, therefore they involve plenty of research, usually. I wanted to make an educational game foremost, but the adult theme also intrigued me, so I was thinking of incorporating it somehow. When I finally came up with an idea, it was already too late to really consider trying it; a week wasn’t going to be enough. That idea was a puzzle game about additive and substractive color theory, which I still think is good enough to archive for a future opportunity. But since it would take me too long to make that, and educational games in general were already out of the question, I decided to just go for the other theme.
Next came the question of how to make any game in a short enough amount of time. I’ve had the idea, for some time, of creating a small engine for text-based games in Flash, which I would use to make a series of games, and which I would also release independently. Trying to plan that proved to be too difficult with my limited knowledge of programming best practices, design patterns, and whatnot. But I figured I could use the occasion of the competition to just hard code a game in that fashion, which would be an easy thing to program, and in the process figure out what kind of structure my code would need to turn it into an engine. So, by making this game, I fulfilled two goals: I entered the competition, and I learned a bit more about programming.
The game is text-only, but it does deal with subjects such as sex and rape, so it is meant for mature players.
The game was created originally for the Ludum Dare competition, and polished during the following week. Coded in Actionscript 3, using FlashDevelop as IDE and compiled using the Flex SDK. For the graphics I used Photoshop and Illustrator, and for the audio I used LMMS and Audacity. (continue reading)
What you see above is my computer screen during the past weekend (each hour reduced to 2.5 seconds), as I make two games for two events that were held concurrently. One is a competition called Ludum Dare, on which, during the 48 hours of its duration, participants are expected to create a game by themselves and ‘from scratch’. The week prior, participants vote on a theme. ‘Advancing wall of doom’ won this time, which is not one I’m too fond of, but I did participate and make a game. Or two, in fact, because for the other event, my usual two-hour Klik of the Month, I made a game based on the same theme.
Heart is the name of my Ludum Dare entry. The game is not final, and neither is the name, so let’s say it’s the competition version’s name. It was inspired by Stephen Lavelle’s Defect. It was made for Flash, using the Flex SDK and coded in Actionscript 3. I’ll probably post more about it in the future, when I decide that the game is finished.
I’ve completed a new videogame—another entry in another TIGSource competition. The theme, this time, is ‘cockpits’. My game is pretty much on the fringe in the way it implements the theme, though. What I originally intended to make was some manner of car driving game, inspired by the original Out Run, since I’m such a big fan of the series, and because I love the aesthetic of that kind of low-tech 3D. I might do this in the future; we’ll see how creating such an engine will go for me. But the game I ended up conceiving, because I only had roughly a week to make it (until the deadline was extended another week), is not about driving anything at all, it is merely about looking; how much more simple can a game’s interface and set of verbs get? You are still in some kind of convertible sportscar, but you’re just sitting on the passenger’s seat.
I’ve coined the term ‘narrative exploration’ to describe Viewpoints, because the very core of the concept is about exploring, but not a physical space, like in, say, Metroid, but, instead, a space of different possible stories—a narrative space. The concept itself was shamelessly ripped from Terry Cavanagh’s Pathways —a short game I can wholeheartedly recommend—, though his execution is different from mine (I’m not quite that flagrant).
Also, for this past April Fools’, I made a variation of Viewpoints and released it as if it were the finished game for the competition. I took the Out Run and Sega inspiration further, and created something quite ridiculous. I call it Winner. (It may be worth mentioning that some of the contents of this variation were taken straight from Sega-made games.)
As of today (yesterday), I am a professional graphic designer. My final project, which I now refer to as Campodecolor (Spanish for ‘Colorfield’), was the same videogame I have been talking about for some time, the one about visual composition. It’s not finished as a project, but an important milestone has been reached: its first purpose has been accomplished, which was to get me my degree. Of course.
Here’s my project report (in Spanish), which is a bit out of date and a bit incomplete, but I guess it shows the main arguments that support my project. I have touched on these a bit in past posts, and I might do it further in the future, because they are based on my opinion that videogames, as an artform, can be a relevant contribution to society.
For my defense I had to —evidently— show the game, and do a presentation of basically a recap of the same points already covered on the report. On top of that, during the past week I recorded some playtests, and edited a brief video with that material to show to the committee that graded my work. It was pretty funny to watch the testers stumble around and finally grasp the mechanics a bit, though some came to the conclusion that the game was more about the music than the visual aspect, which, I suppose, is a compliment to the sound design in the end.
I have uploaded the version of the game that I presented today (yesterday). The algorithms are still lacking, I’m afraid, but I plan to make them my top priority now. The dynamic audio is created using the minor pentatonic scale, with the sound of a Rhodes piano, as recorded by Guy Cockroft. I’m glad it sounds as well as it does, considering the notes are selected randomly from the scale. Since it seems to be crediting time, I have to thank Stephen Lavelle and muku for their invaluable help and suggestions on all aspects of my game. Also, of course, my teacher throughout this whole process, Eduardo Castillo. (continue reading)
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.1 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)
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,1 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)
