So… First LD for us and how we’ve learned:<\/p>\n
We had a team of two people, one mostly did coding and the other one all the art. We didn’t submit our game because we didn’t finish it in time. However we have learned quite a few valuable lessons in game dev and in participating LD, so here they are:<\/p>\n
Framework and Library:\u00a0<\/strong>It has been said like a thousand times over and over: Make a framework with the core parts of your engine before you start LD. Really, I thought I would be able to actually pull it off without, and I’m quite a good programmer, but it took me more time than expected AND all the time I put in the framework was – now that I look back at it – actually needed for adding gameplay (top priority) and features (such as music and sounds). Also: if you’re going to use a library make sure you know how to use multiple features. For example: We used slick2d with java, because slick2d is based on opengl and it makes rendering a great deal easier. But slick2d has so many awesome features (like: particles, entities, animations etc.) that I didn’t use\u00a0and programmed all by myself (which equals loss of time)\u00a0<\/em>that now, looking back at it, makes me feel stupid not using.<\/p>\n Graphics and Sound:\u00a0<\/strong>To be honest: we didn’t even start on music and sounds. We planned this for the final day, but because of certain reasons partially explained uptop we used the final day to add more levels and other gameplay mechanics. The graphics however were done nicely (in my opinion). However if we look at graphics other participants made, we do understand that our level of detail and skill isn’t as high, but that’s ok right? Everyone needs to learn, and that is what this was all about for us. But for the graphics I will say the same as for our library and framework: Practice it beforehand, make some standard assets or at least a scheme with colors and techniques or something that you can use to remind you how you should be making art in a way it fits you.<\/p>\n Working together:\u00a0<\/strong>Working together was really ok actually. My teammate and I we’re actually able to help each other (mostly) and because we split the work mostly into art and programming we weren’t interfering with each others work. One thing to keep in mind though: When one has been programming almost everything and the other one needs to program something, make sure you understand a certain train of thought in the projects code. We had a small problem where my teammate had to do almost extensive research (yeah I like to exeggerate a little :3) to find out how to render particles or a newly added entity. And really: it wasn’t really a big problem for me to explain it to him, but again: this is a way to lose valuable time.<\/p>\n Game and Gameplay:\u00a0<\/strong>Just a little bit more about the game itself. We had an idea right away to give the player a teleportation device of some sort in the first level. This device would grant the player acces to several layers of time of that level (environment). This way the player needs to solve puzzles and get to the portal at the end of the level. We eventually made three levels: The ‘now’ layer, in which the player starts, the ‘medieval’ layer and the ‘dinosaur’ or prehistoric layer. Every layer had it’s own level design and has buttons and (movable) walls etc. which made it one big puzzle. There are enemies shooting at you, and you’re able to defend yourself etc.<\/p>\n Eventually we finished two complete\u00a0levels\u00a0and one level was still in development at the end. Again, if we look back at the features we’ve added, I can say we we’re having the, how do you call it, feature disease? Anyway, again a valuable lesson for the next time: Focus on primary gameplay, not awesome little details that are less important. In our\u00a0case that is: First some playable levels, not nice little particles for everything that happens in the game.<\/p>\n <\/p>\n I hope our experience will help you guys as much as it helped us. I’m quite sure we’ve all been at this point, if not we will get to this point.<\/p>\n TLDR;<\/strong> <\/span><\/p>\n + Make sure you have a frame ready before you start LD;<\/p>\n + Make sure you understand the library you’re using;<\/p>\n + Practice the making of assets before you start LD and perhaps make scheme’s or dummies of some sort;<\/p>\n + Make sure you understand each others train oof thought (not only for the jammers, this is a good advice from a person learning software engineering)<\/p>\n + Focus on primary gameplay FIRST, nice little details can be done later when you have spare time.<\/p>","time":"August 26th, 2014 12:38 am","title":"Ludum Dare 30 Jam \u2013 Post Mortem"}