The port had an interesting set of challenges. The game should use the original levels and everything including player movement and enemies should be exactly like it was on the DS. Obviously I couldn’t use any of the original code directly, but it was still useful to be certain about some enemy behaviours. The level files had to be exported, converted into a proper format for the AIR game and then read back.

For that game, I worked together with another programmer. My part was almost all the in-game gameplay, i.e. level loading, platforming and implementing the player character, the enemies, the various other hazards and the pick-ups in the game world.

Here is a trailer – in German, but the gameplay is still easily understandable:

The first one is Beer Pong HD for Android. Back in the days when I worked in the Netherlands as part of my studies, I made its first version (further on, other developers expanded it) with Unity for Codeglue.

It seems the original promo video is not available anymore. Here is the best video that I found (made by Androida.it). I suggest you jump to 4:16 for gameplay:

What is still available is the video how the AI finds out which ball throws end up inside a cup. I didn’t just want to calculate how to hit the middle of the cup because that might look too artificial, but I still wanted to be able to predict whether a throw hits, even if multiple jumps on the table or cup’s edges are involved. Here is a video of the AI “training” and finding out which throws hit:

(And the best part is that it takes some time and is automatic. Time for a cup of coffee – or an office sword fight. I like being a programmer.)

For a workshop at the YOU, a youth culture fair, I was asked to make a concept for a short game programming workshop.

The requirements were:

• The workshop should give an impression of the work of a game programmer.
• It should take about 15 minutes and allow groups of varying size.
• I should assume that the participants have no experience in programming at all.
• Instructions should be kept to a minimum; the focus should be on hands-on experience.
• The workshop should produce a quantifiable result.
• It should be an enjoyable experience.

No easy task. Luckily, inspiration struck, and a few days later I finished the game StarCoder.

StarCoder

Move the player to the star by using
Left/Right and Space to jump.

An easy game if it weren’t for the spikes –
or if you could jump far enough, for that matter.
Luckily you can edit the source code.

There are 15 distinct solutions to win the game.
How many will you find?

Download for Windows

Source Code (License: CC BY SA)

The Workshop

The workshop went extremely well. Everybody found at least 4 solutions, with some finding up to 10. The game also seems to be surprisingly fun, even (or especially?) for non-programmers! Results were often accompanied by laughter and some of the participants even asked for the program so they could try it again at home. And I remember a teacher who sat down to try it himself after I finished the workshop with his group of pupils.

If you use it yourself (which I’m totally fine with – I’d love if you drop me a message that you are using it!), this was my approach:

• Tell your attendees that the goal of the game is to get to the star. Ask them to click in the left part and try it themselves: Arrows keys to run, Space to jump.
• After half a minute admit that it seems rather impossible – but luckily there’s the source code on the right side which they may edit. Ask them to notify you once they have a solution.
• Once they have the first solution, congratulate them for their achievement. Then ask them to click on “Reset” in the lower right corner and tell them that there are 14 more solutions.
• After a few minutes (or a few solutions, depending on their speed), tell them that there’s also the “Creation” tab in the upper corner.

The ideal number of attendees seems to be 1 to 3 per computer. You might want them to write down their solutions if you want to assign a score to each group later.

So… how about you? Did you find every single one of the 15 solutions? Try it yourself first – and then check it with this handy walk-through. (No cheating though!)

And if you’re interested how hard solutions are and which are found the most and least easily, you can check out these statistics (contains spoilers!).

Credits

• Concept, Programming and “Art”: Tobias Wehrum
• Sounds: Moritz Ufer

Thanks to my playtesters: Moritz, Tobias, Kelvin, Sebastian, Simon, Christiaan, Lukas, Florian, Marina, Jana, Jens, Paul, Ronja and Nadine. You guys have been a huge help!

Made in cooperation with:

• Mediale Pfade
• Stiftung digitale Spielekultur