In development: The dictator (working title)

So this is the current AGS-project I'm working on at the moment.

The "enigmatic" ruler of a small tropical island banana republic is being overthrown by the people. Apparently they do not understand the true reason why the president has been flushing the state finances, being of course that he has taken it upon himself to personally protect the island assets in case of an emergency. Such as a hack-attack draining the island funds or war.
However the people do not know what is the best for them and is now trying to overthrow the president. Help him out!

The game is a traditional point-and-click adventure and development progress so far is: Design and puzzles are about 100 % complete, however everything else is kind of pending and I haven't started any scripting yet, as I don't have any art yet.

But... here's sketches of the unnamed president.

Reflections on: Hello Neighbor!

Hello Neighbor! was my second fully developed game and was made for an assignment in my class. The assignment was basically just to fully create (involving) coding a game by yourself. The development time of this game was less than a month, starting about end of september and releasing in mid-october 2010.

The game was made in the AGS-engine, as it was the only programming experience I had and I didn't feel like I wanted (or could) learn a new programming language in the short amount of time, I had to make this game.

It's a very short puzzle-exploration game about making the residents of a small apartment block interact with each other.

Positives:

• Complete. By which I mean that I am happy with the completion level of this game. The artstyle was consistent (although again, not very pretty, and also kept in the same vein as The wife who wasn't there in order for me to save time and recycle some interface elements) and also every single action in the game had a unique feedback. This took me quite a lot of time to think of all the different reactions but I'm happy that I did, rather than just copy/pasting the reactions. I like to think the player will be more tempted towards playing again, knowing that all the reactions are different from each other.
• Within scope. This is the first game, I've developed with a deadline, so I am happy I managed to set up scope for the project that I allowed me to complete and polish the game. Instead of just barely managing.
• From scratch. This was also the first game I created from scratch (coding wise) as I used a template for The wife who wasn't there. This boosted my confidence slightly in the coding department and also makes me willing to try and learn other programming languages rather than being afraid of coding, as I was before.

Negatives:

• Lack of motivation. The game lacks a motivating factor. When I conceptualised the game I thought: "Of course, people will play and find this game interesting." However this was based on the fact that I thought the different reactions of the residents would be enough to entice player to explore the game. Originally there were also far more residents rather than just six, which of course makes the amount of unique solutions even bigger, but as I scaled the game down and tested it myself, I realised that reading the responses might not be that great. So I introduced the cheap solution of a trophy/achievement system, which actually did the trick and afforded multiple plays, which had been my goal.
• Lack of sound. There is not a lot of sound in this game, and sounds and music in general are not my strongest points. The lack of sound makes the game rather "empty", although the little sound I did have in the game, I was happy with, as it conveyed the theme and simplicity of the game, I was especially happy with the whistling my brother did for me in the main menu. However the lack of sound is still a bit disappointing, and I probably should invest a bit more time in this department in the future.
• Consistent (but yet slightly boring) artstyle. I was very happy with the consistency of the artstyle, but yet with such a simple game as Hello Neighbor! is, it comes off as a bit boring. But I stuck with this artstyle due to the fact that it is fast and also because it allowed me to recycle art from The wife who wasn't there. However I feel now that perhaps I should have tried a different artstyle for this game, as it is so simple and consists of not that many assets. A more exciting artstyle would probably have improved the experience of this game immensely.

Overall I'm happy with this game. It's not very big or very beautiful, but it is complete, simple and easy to get into and also it afforded some replayability (not much though) which I am happy with. Also I was within scope which is good and this also gives me some sort of insight into my ability in regards to the time I need to finish games.

In development: The balloon game (working title)

So this is the game I'm currently working on at MTG. We're reaching the final stages of development with only about two weeks to go before deadline. The team consists of Jens Højlund Lauridsen, Troels Frostholm Mogensen, Emil Norsk-Nielsen and myself.

Basically it's a browser game about a boy from space who has been left behind on earth, with the help of a balloon and people he meets on the way, he will now try to make his way back to his home planet.

I am completely in charge of art in this game which reflects in a rather childlike and innocent artstyle, taking a bit inspiration from Paper Mario (with the white borders of objects) as well as Yoshi's Story with a fairly flat and significantly different background.

In the earlier concept art, the boy as well as the general look of items had a thick black outline whereas background objects (such as the island beneath) had a watercolor painted style. However the black outline caused problems as the blue background got darker further up making it impossible to see the outline. This is why we/I ended up going for the white paper cut-outs. 

The background also changed from the impressionistic painted to a more stylistic shaded look (compare between the island in picture 2 and the background, picture 4). The reason for this was partly because the new look afforded more detail, I was inspired by drawings from another member of the team and also because I couldn't find the brush I had used earlier for the impressionistic look.

¨

 

Reflections on: The wife who wasn't there

The wife who wasn't there was my first fully developed game about a husband who came home from work only to find that his wife was gone.

The game is a fairly traditional point and click adventure game made in the Adventure Game Studio engine by Chris Jones. The development time of this game was about 8 months on/off, starting with concept development and puzzle planning from september 2009 (although the story idea was from 2008), actual production (writing/scripting/drawing) from january 2010 and published on bigbluecup.com in late April 2010.

Positives:

• An experience and proof to myself that I could actually make a game. This game definately boosted my confidence as designer.
• General good feedback on the puzzles. This was something I was very worried about, since I didn't have a lot of confidence in my puzzle-designing skills, so it meant a great deal to me that players could figure out how to solve the puzzles and that they were logical and apparently also easy. However easy is not a bad thing in my book, as I think there is nothing worse than being stuck at a puzzle in an adventure game.
• Consistent artstyle. This is something I spent a lot of time on, making every single item, button and cursor look consistent, so I was rather happy it was acknowledged. It might not be the prettiest game, but it looks like it all comes from the same universe, and communicates my ideas and also the simplicity of the story.

Negatives:

• Lack of visual distinction between interactive vs. non-interactive objects. This partly comes down to the artstyle which doesn't differentiate between different kinds of objects but also because I didn't think of adding a rollover function on the objects. So the player would actually have to click objects to know whether an object can be interacted with or not.
• Some weak puzzles. Even though I did get good feedback on the puzzles, there were still some weak ones around. Such as "non-existent puzzles" puzzles which are basically not puzzles but rather something the player randomly stumbles upon and solves without any involvement except clicking on an object.
• Lack of direction. This was something I noticed when watching my cousins play as they didn't really understand what they were supposed to do when the game started. I believe this is due to a lack of information at the beginnning and the motive to play the game might not be clear enough in the game itself. (The motive being, that the husband has to remember what his wife told him yesterday)
• Room design was slightly icky. By this I mean that not all rooms had apparent exit/entrance ways, so players didn't always know if walking to the edge of the screen would lead to another room or to nowhere. This would probably be improved with some sort of visual clue, for example doors or carpets leading off the screen.

Overall I was/am satisfied with this game despite it's many flaws, it was a good learning experience and I have learned both to keep a consistent artstyle but also how to use the AGS engine, which makes me more prepped towards doing more adventure games. I've also gained quite a lot of confidence in my puzzle-designing skills and quite a lot of do's and dont's for the games I'm working on now and for the future.

Hello world!

So...

I've jumped on the bandwagon and decided to start a blog.

This blog will mostly be used as developing diary for the games, I'm working (or should be working) on, and I suppose venting out the progress (probably only to myself) will possibly help the development move along.

I'm hoping this blog will also be useful as a reflection tool, as I usually don't reflect (at least formally) on what I do and have done. Putting my thoughts down in blogform probably help force me to think about things I normally just gloss over.

Lastly, if anyone actually reads this blog then: Hello to you! And I hope this blog makes an interesting read.

And here's a penguin.