I am not sure postmortem is the proper term for this entry, being I can’t be sure the life of the project has come to an end. Perhaps it has. Regardless of the lifetime of the project, this post is about what happened, what went right and what went wrong, as I worked on my Ludum Dare 21 entry: Escape. Sorry, I made the “what happened” a little longer than I expected, skip to the bottom for a true post mortem.
Ludum Dare 21: Start – 1 month:
This weekend started at least a month before with preparation and cleaning my slate for the entire weekend. I made it clear to family and friends that I would be busy during the weekend. Under no exceptions, (perhaps a big pay bonus), was I going to go into work; regardless of the circumstances or consequences. Luckily work didn’t want me to come in, so I didn’t need to worry about consequences. I had my framework picked; homegrown DirectX 9 engine written in C++, my language of choice. I was set. The week leading up to Ludumdare I made a blank project from my template – in doing so I felt I’d automate this process; which took me the full week nights after work. However, I can now type “CreateProject ProjectName” and out comes an already compiled template project that is at blank screen and ready for development.
Ludum Dare 21: Start – 5 hours:
No lie, there were several ideas floating around my head and was hoping for Castles to be the theme. I went shopping for some food and supplies for the weekend so I didn’t need to waste time doing so later. The IRC channel; #ludumdare was insane, I started a G+ hangout that filled with so many people, and I didn’t know them all, but we all shared a passion for Game Development. Finally, it was time.
Ludum Dare 21: 48hrs Remaining
Theme: Escape. Thoughts crossing my mind, #ludumdare going insane, I left the G+ hangout and went to my white board, and to cook a meal while I thought up ideas. I was pretty surprised that I had three right off the bat, each with their own challenges. One was a turnbased puzzler that would have been easy on the programming side, harder on the content side. Another I threw away based on scope, it was much too big for a weekend. The final was a physics based glider falling through a maze like puzzle to the ‘exit’. Despite being harder with math and level design, I choose the physics based glider on the basis that content would be kept to a minimum.
Ludum Dare 21: 44hrs Remaining
I had created a 2D camera, and sprite class – two things I overlooked on my framework, which admittedly is typically used for 3D projects. I managed to get the basics going before heading to bed to sleep on my idea before committing completely.
Ludum Dare 21: 36hrs Remaining
Woke up, ate a good meal and planned to work on the physics of the glider until I got it right, so that I could avoid wasting time on level design by setting the physics in stone before a level is started. The physics gave me some problems, it took awhile to figure out that the equation for lift did not apply it in the correct direction. That and other strange things. I spent far longer on the physics that I wanted, and I never got quite what I wanted out of it – but it was somewhat controllable.
Ludum Dare 21: 24hrs Remaining
I spent about 2 hours trying to get a randomized tunnel to generate, and quickly gave up on the basis I didn’t like the outcome of any of the work. So at this point the choice changed to making a quick and dirty level editor, which actually came out very well. By the time I went to bed I had wrapped up a level editor that I could play, edit, play, edit in quick succession. Hung out on G+ hangouts as much as possible, had some good discussions while still getting stuff done.
Ludum Dare 21: 13hrs Remaining
Motivation has dropped quite a bit even though I was on the final stretch. Time pressure was starting to begin as I realized I didn’t have a level or anything – but I did have my main gameplay mechanic; physics. To accurately test the level I was about to develop, I needed to add the collision for the game – which was much more difficult than it seemed. Despite using code I had from another project for line-to-line collision, it did not work. In the end, debugging proved that I was putting in the wrong lines… Many hours wasted.
Ludum Dare 21: 6hrs Remaining
A final burst of energy to finish the level, add a score counter, title page and share it on #ludumdare – got some feedback, made a quick and dirty tutorial page – that added a lot to the look and feel of the game. Removed the level editor and temp map files for the final build. Tried making some music for the game, but failed miserably.
Ludum Dare 21: 0hrs Remaining
Submitted the project as a jam on the basis I did not share my code. However, I followed every other rule strictly.
Ludum Dare 21: Postmortem; What went wrong
- This was the buggiest project I’ve worked on in years, I had to cross hurdle after hurdle; physics, line collision, level design.
- I did not put enough effort into created the game music, or sound effects – and this would have paid off huge in the end.
- My own expectations were let down on basis of; physical feeling and level design.
- Although I took a good share of breaks, getting out of the apartment would have been useful.
Ludum Dare 21: Postmortem; What went right
- The visual quality stunned me, it actually came out looking decent.
- I made good use of breaks for food, shower, sleep, and thinking.
- I finished, it was close to complete, and I had a lot of fun.
Check out the project, rate it, leave comments and most of all – hopefully it is enjoyable, even for a few moments.