My Milked Week

Ludum Dare

It’s been some time since my last post. To be honest, I was kind of disappointed after my Ludum Dare Brave Warrior entry. I got nothing but good critiques and feedback, but the score didn’t reflect that. Not that I care about getting a high score, but the lack of negative feedback left a bad taste in my mouth.

I’ll join the next LD, albeit under some extra time constraint: I have a concert to play with my double bass class. Perhaps I’ll join the Jam, I don’t know yet.

Running projects

I have a few things going on, but the two big projects I’m working on right now are

- Brave Warrior- Network Game

I started Brave Warrior as a remake of my last ludum dare entry, but I got sidetracked a lot and it’s turning into this whole other beast. I guess what I wanted yarpa to be. Right now I’ve turned it into an RPG with unspecified mechanics. I’ll publish a first test somewhere this week or next week. More information will follow in its own post.

The network game is an idea I had a couple of months ago. I won’t elaborate on it, but it’ll be awesome.

Play Store

I also made an account in the Google Play Store and I’ve pushed my first alpha build onto Google Play.

LD26 Post Mortem and #1GAM

Short LD26 Post Mortem

The results are in for Ludum Dare 26. I’m not as satisfied with the results. The scores are average, which is ok in itself. But I’m somewhat disappointed that there weren’t any negative or “average” feedback comments. There were people out there who didn’t enjoy my game as much and they didn’t share why or what was wrong with my game.

I’m not going to rant, but I put in effort to give feedback (positive or negative) to (most of) the games I played. I expected the same in return. Not going to rant.

Anyways, onward;


There’s an initiative I wanted to join some while ago: One Game A Month. The goal is simple, make a game each month and share it. So, starting from July, I’m going to finish a game each month. For my first month, I’ll take it easy and make a simple puzzle game. Nothing to serious or new. Just some tried and true mechanics to get me started.


Groovy and Tomcat, Pt5 – Bringing it together

For the final part in this miniseries I’ll create a small web application which brings together everything discussed so far. We’ll be using a Java Servlet, a Groovy Servlet and Groovyscripts to bring you the ultimate mix of all things Groovy that aren’t GRails.

What does it do?
It counts the visits you make and adds them to either the javacounter or the groovycounter. There is also a small groovyscript resetting the counter.




<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<%@ taglib prefix="c" uri="" %>
 <p>Calls made:</p>
 <td><c:out value="${javacounter}" /></td>
 <td><c:out value="${groovycounter}" /></td>


request.session.setAttribute("javacounter", 0)
request.session.setAttribute("groovycounter", 0)


Java Servlet

public class JavaCounter extends HttpServlet {

 protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {
 Object countObject = req.getSession().getAttribute("javacounter");

 int count = 0;

 if ( countObject != null ) {
 count = (Integer) countObject;

 req.getSession().setAttribute("javacounter", count+1);


Groovy Servlet

class GroovyCounter extends HttpServlet {

 protected void doGet (HttpServletRequest req, HttpServletResponse resp) {
 def countObject = req.session.getAttribute("groovycounter")

 def count = 0

 if ( countObject != null ) {
 count = (Integer) countObject

 req.session.setAttribute("groovycounter", count+1)


And that’s the end of this series. The code can be checked out at:¬†

new directions

Or to put it better: a new life for this blog.

I used this blog, or tried to, as a reference to all my games on But meh, I might update the blog to include all my games I played, but I couldn’t be bothered back in 2009 and I certainly cannot be bothered in 2011.

I’m restarting this blog as I’m going to be a participant in Ludum Dare 22 and I want to blog about it (and other stuff). Ludum Dare is a “competition” that last 48 hours, one weekend long, during which you (try to) code a game from scratch. Using libraries and tools is allowed, but the first letter of code is written when the competition begins. “What does one win?” Pretty much nothing. Why enter? Because.

Yeah, because.