About netmute (twitter: @sier)


Ludum Dare 28
Ludum Dare 27
Ludum Dare 26
Ludum Dare 25 Warmup
Ludum Dare 24
Jam o'Clock #01
Ludum Dare 23

netmute's Trophies

netmute's Archive

Timelapse for “One fine morning our machines will cut us down”

Posted by (twitter: @sier)
Saturday, May 4th, 2013 5:40 am

2 days of blood, sweat and tears compressed into 15 minutes.


Day 1


Day 2


Play and rate here

Make a timelapse video on Mac OSX

Posted by (twitter: @sier)
Friday, April 26th, 2013 12:07 pm

Most of the tools available are expensive and/or stupid.

So here is a very simple ZSH script I wrote:


# Takes a screenshot every n seconds (Only works on OSX)
i=1; n=1
while [ 1 ]; do
screencapture -t jpg -x ~/Desktop/screenshots/${(l:8::0:)i}.jpg
let i++
sleep $n

# Turn screenshots into video
# cd ~/Desktop/screenshots/
# ffmpeg -r 18 -i %8d.jpg timelapse.mov

I hope this is useful to some of you.
See you on the battlefield :)

Here we go again

Posted by (twitter: @sier)
Tuesday, April 23rd, 2013 5:08 am

This will be my 1st year Ludum Dare birthday 😉 Let’s have some fun!

Tools I will be using:

  • Language: Coffeescript
  • Engine: Impact
  • Editor: Vim
  • Graphics: Pixen
  • Sound: Bfxr

Obligatory crime scene photo:

Netmute's desk

You may also be interested in a game I build a month or so ago. It’s called Parkour:


We all know what the theme will be

Posted by (twitter: @sier)
Friday, December 14th, 2012 5:50 am


Dev diary / post mortem for Tiny Maze Speedrun.

Posted by (twitter: @sier)
Tuesday, May 1st, 2012 9:30 am

Now that a week has passed, it think it’s a good time to summarize the experience that has been my first Ludum Dare.

My very first attempt at making a game a year or so ago kind of failed. The text-only action RPG was basically just a fighting engine. It was playable, if you were able to install and run the thing. Ruby was the language I knew well, and so I made the game in it. But distributing Ruby games is a pain. Installing it was almost impossible without deeper knowledge of the Ruby ecosystem.

Fast forward to one week before Ludum Dare 23.

I somehow decided to give up my resistance against having anything to do with JavaScript, that I kept for so long. One of my colleagues at work is some kind of JavaScript genius, and he recommended a few learning resources to me.
After having read one of the books for a couple days, I felt I wasn’t really learning anything. I needed a project.

Luckily the 10 year anniversary Ludum Dare was that very weekend. I always wanted to participate in Ludum Dare, but never had the guts. I finally came up with the crazy idea to jump head first into a 48 hour game making competition, using a programming language I’d been barely exposed to. Even if it would be a complete failure, I would still learn a ton.

I live in Germany, so the theme announcement was on Saturday at 3am. I spend Friday evening googling for a usable JavaScript game framework. I found Crafty.js, set it up, and made myself familiar with the absolute basics of how to use it. Crafty.js is great, much better than anything I found in the Ruby world.

My girlfriend was visiting friends on that weekend, so I had plenty of time. My plan was getting a good nights sleep, get up around 9am on Saturday, read the theme announcement, and then think about it, while having a shower and breakfast.
Then I would start coding around lunchtime, be finished with the core mechanics when I go to sleep, and have the whole Sunday for sound, graphics and polishing.

Overall that plan kind of worked. I started panicking when, after a couple hours, I still had no idea what to build. The time constraints put immense pressure on me and I felt way too stressed. I had to remind myself that I was doing this for fun and it wouldn’t matter if I failed.

After calming down, I decided to just start coding without having a concept. Looking for level generation algorithms, I stumbled upon recursive backtracking, and started implementing that. Turns out implementing algorithms in a language you’re not familiar with is quite a challenge.

By saturday evening I had a pretty good maze generator, a way to draw the maze on the screen, a blue rectangle that I could move with cursor keys, and collision detection. But still no idea what the player actually had to do.
The best I could come up with was an exit you had to reach in the shortest amount of time possible. Maybe a few powerups and obstacles along the way.

When I stopped coding at around 11pm, there was a timer and an exit, which would stop the timer when reached. I looked on what I had and was quite happy with the output of one day. Before going to bed I spend an hour playing my game. And realized it was fun. I couldn’t have been more happy at that moment :)

Unfortunately I overslept on Sunday. After breakfast and showering it was 12am.

I opened Pixen and started drawing animation sprites for the player and exit. I figured the reason the player needs to run around in a maze was that he desperately needed at toilet. I gave the walking animation some urgency, which I think turned out quite well. Especially since I had never drawn sprites before in my life. I made the sprites 8x8px to pay at least some credit to the ‘Tiny World’ theme. Then I made the start and exit screen in Pixelmator and built a very basic main menu.

It was hard to focus after my girlfriend came home at 5pm. So I decided to ditch powerups and sound, and instead fix the remaining bugs, wrap the whole thing up, and submit it.

Play and rate my game here:



What went well:

  • I learned A LOT of JavaScript.
  • I learned to actually like JavaScript.
  • I drew a little pixel dude and love the outcome.
  • After the first stressful hours, I enjoyed the weekend.
  • I finished a game!
  • The game is actually fun to play.
  • Great result for first time Ludum Dare, first time JavaScript, first time Crafty.js, first selfmade graphics, and first finished game.

What could have been better:

  • There is no sound. (Turns out proper audio is incredibly hard to do in JavaScript, so it was the right decision afterall.)
  • I couldn’t build all the ideas I had into the game.
  • I wasn’t able to come up with a good game concept that matched the theme.
  • Crafty.js has a few bugs/limitations that took me a lot of time to work around due to lacking JavaScript experience.
  • Concept and name of my game are the most uncreative anybody could come up with.

Experience gained:

  • I need to be alone to be able to really focus on something.
  • Building games is awesome.
  • JavaScript/html5 have boatloads of limitations when it comes to building games.
  • Have a basic idea what you want to build BEFORE the theme is announced.

After the compo

What really stuck with me is how awesome and friendly the Ludum Dare community is. Almost everyone had something nice to say about my game, even if it isn’t much compared to the other entries.
I will definitely participate again.

I continued working on the game, to implement the missing powerups and sound. And I made sprites for the walls as well.

You can find the improved ‘after compo’ version here:


Thanks for the awesome experience everyone!

[cache: storing page]