Goat 666 – post mortem

Posted by (twitter: @PolClarissou)
December 18th, 2012 12:34 pm



It was my very first time taking part in a Ludum Dare, but I already did make some games and one game jam with friends of mine, so I wasn’t new either to technical aspects of gamemaking nor to the 48 hours time limit. In the end, I find my game quite satisfying, except for its difficulty wich is a little bit excessive.

 Play Goat 666

So here comes the post mortem :


-As I said, no big surprise during the making of the game. I didn’t get unexplained errors while coding, and didn’t spend too much time on deciding how the graphics would be done (except on the cover art).

-Good time management. Even if I became less and less efficient as I got tired, I endend up having some hours left to polish everything, which I wasn’t sure of at the beginning. It may only be chance since I didn’t really plan anything :B A good thing is that I decided quite precisely what I wanted to do right from the beginning, so I didn’t spare time thinking of what I should do after that : I knew where I was going and how.

-The experience was really enjoyable, even if I felt totally destroyed after that 😀

-Friends. Lov’em.


-Unconvincing game mechanics. I don’t feel like my game actually is really fun in its gameplay, even if the music and the graphics make it more nervous.

-Unbalanced game : although I managed, in the end, to tweak a little the probabilities and enlarge the hitboxes of the people you have to click in the game, the difficulty is still quite high. I usually make this mistake of forgetting that people who will play my games for the first time won’t be used to it as I am since I’m permanently testing it, and thus that I should make it easier even if I can beat it quite easilly. One day I will remember it.

-I don’t code fast enough..

-Couldn’t really get any sleep D: I tried though, but too much tea, coffee and not being at home (thus only having a sofa to sleep) broke  the mood. So I ended up being really really tired and slow at working.

-I used musics from other artists, which forbade me to submit my game in the compo, so I moved it to the jam. I didn’t read the rules with enough attention and though it would be OK if I used free-of-use tracks. This is no big deal, but it’s kinda annoying since I made everything else by myself within the 48 hours, so… Well, I’ll be more careful next time.

-I wasted time writing posts because I wasn’t always sure of my english. Nothing grave, but still, it’s kinda stupid to spend 5-10 minutes on a five lines post 3:


-Spare more time on looking for game concepts, and learn how to do it more efficiently. It’d be nice to have a really fun game for once.

-Learn how to make music, for heck’s sake D:

-Maybe start working with 3D in order to get moar skills, even if it’s quite hasardous for now.

-Keep washing the dishes when I get too tired/upset to do anything right. In the two game jams I made, there was that moment when I just finished something and I though “Okay I really need a break right now, but I don’t feel like sleeping, and I’ll get even more upset if I just stay there doing nothing”. And seriously, washing dishes is the best thing to do at that moment 😀 It’s totally mechanical, so you don’t have to concentrate while doing it, and it’s more relaxing than doing nothing. Well, maybe it’s just me…

-Do games ! More games !

One Response to “Goat 666 – post mortem”

  1. Wuhao says:

    I played your game, Its not a bad concept, but the idea o sperating your core game play into 2 parts is not good

    by 2 parts I mean, 1, you have to avoid getting shot, and 2 kill people. those 2 parts does not have a strong connection.

    my suggestion is that you should somehow merge those 2 gameplay, eg. you fly near some man to “pick him up” you could them swing him around like attached to a rope.

    my second suggestion is that those people moves too un-naturally, this causes many frustration to click on them, you shoud ease their movements, people don’t make shark movement like that.

Leave a Reply

You must be logged in to post a comment.

[cache: storing page]