|Original design sketch.|
I was trying to stay away from writing a post mortem for this game because I don’t want to accept that it’s over. Multiplatform support, multiplayer networking, a 3 (occasionally 2, but usually 1) man development team and a very short project deadline; this was clearly one of the most challenging projects I ever did. It was also the most fun. From the all nighter brain storming session with Jeryll, Angelo‘s wonderful design inputs, game design arguments with Lomel (ex. Should Maria Makiling have a “Wrath” meter that allows her to nuke the whole place?); the whole creative process justified the reason why I chose to make games: it’s way more fun than just playing them.
However, coming from a software engineer’s perspective the project piled up with mistake after mistake that the game would have come out mediocre at best. And it did, actually. The game wasn’t there during the first opening night and it was barely enjoyable when it came out in the second.
What Went Wrong?
Choosing the wrong guns
During the initial planning, I was the only game programmer present, and a very inexperienced one at that. Multiplatform? That leaves GameMaker out. Multiplayer? Hmm, Java has nice networking features. Graphics requirements.. ok there’s no way we can render something that intensive in Flash. I chose Flash and Java anyway for the main reason that Flash is actually more multiplatform than Java, and Java will handle Flash’s networking. I was in the middle of creating my game engine in Flash when I posted this..
That’s right, I can’t make the animations smooth enough for an enjoyable game experience. So I went back to Java. I chose an old Java game framework called JGame and Sun’s Project Darkstar Server. Both frameworks looked easy enough. I put aside JGame since it was the least challenging and began working on the Server Side.
Bad choice number 1. It was too late when I realize that JGame wasn’t a good choice programming wise because it hardly implements any OOP, and there were already two programmers sharing and modifying the same java code file. Plus it became a headache just trying to locate java functions inside a 1000 plus line single file source code.
Bad choice number 2. Choosing to work on the network servers before even creating a working game. I thought that if I finish the hardest part, then everything would be smooth sailing from there. What I didn’t saw, was the possibility that I just might not pull off that hardest part. Blinded by my inexperience and my pride to do something only few developers even attempt to do, I marched on; with the rest of the Biomodd guys not seeing the semblance of a game coming out from my computer screen.
This was a case when a rapid prototype would have benefited the project greatly. More people could have played the game even if it was still on beta. Playtesting and balancing would have been done based on their inputs. And more buzz would have been generated about the game.
Lacking the right tools
Remember Java’s “write once, run anywhere” credo, well, I never realized how much of a fantasy that was until I tried running the server and the client on Ubuntu. I never anticipated the screensize not automatically adjusting plus the sound not working on Linux. Add the extra work of uploading the necessary .jars and you have yourself a big problem that would’ve been easily solved if I used multiple Virtual Machines on my laptop.
I was also using Vista x64 which much to my disappointment, being the fanboy that I am, crashed every time my development processes took 100% of the memory.
|Jeryl in the lab|
What Went Right?
Changing Horses in Midstream
And having the courage to do so. I have been ignoring Slick2D up until 3 weeks before the Manila exhibit. I realized I can’t go on with JGame and if I continue trying to make it work the code is going to be worse and worse. Slick was actually pretty easy to jump into and I recoded the whole game in just 2 days. The transition was painless I even added some extra holes in it for the networking layer.
The code base itself became more stable and extensible that it just took me a little more than an hour to add the 2-player and Twitter features.
A lot of the features originally stated in the game design didn’t make it to the final game (or at least the game that was played in the exhibit). My inadequacies in programming skills prevented me from creating a stable networking layer. Hardware issues made receiving data streams from environment sensors a difficult task. The way we intended to represent Maria Makiling seemed impractical considering our lack of artistic skills. We also have to let go of the much debated Wrath issue of Maria Makiling. It looked as if the features that made the game fun on paper weren’t going to be part of the actual software.
Then, 2 weeks before the end of the exhibit, I made some of the few good decisions I made in this project.
- Put the game source on code sharing.
- Dropped the networking layer altogether.
- Made a single machine 2 player game.
- Connected the game to twitter.
First, I shared the game in Google Code. This way the game can finally declare itself open-source. (Well, not really that open, outsiders only have read privileges). It didn’t actually contribute anything development-wise, but putting it up there made the project “immortal”. The installation may be dismantled, its parts distributed or recycled, but the software and the source will always remain in the clouds free for anyone to check out – and/or laugh at. (Which reminds me, I might need to clean up the code a bit for those who are allergic to duct-tape coding).
Second, I made the painful decision to let go of the highly unstable networking code. It was becoming a monster and working on it ate a lot of valuable dev time that should have been spent on improving the gameplay. Throughout the project, the multiplayer feature took the highest priority; the game cannot be the game if it wasn’t multiplayer, the game design hinges on that. Also, call it programmer’s ego, but the thought of giving up on the coolest thing you have ever coded simply didn’t enter my thoughts during that time.
It was after taking a few days off that it finally hit me. There simply isn’t enough time to pull off what I’ve been trying to do. And it wasn’t that I was giving up on my code, I simply saw a different way to write it. The networking layer needs to be taken down, but that doesn’t mean the game had to change. In fact, releasing it on single player for the exhibit was already shameful in my part.
The game should only be played with other people. So I settled with the easiest option: make it 2 player. With only a few days left on the exhibit, I thought it was too late.
Lastly, there’s “the game tweets” decision. Originally, Tina, the electronics ninja, setup some sensors to connect to the internet and visualize the state of the installation. The game was supposed to hook to that as well, creating a unique interaction that fuses everything in Biomodd together. Sadly, because I was too focused on unimportant stuff (curse you, networking and parallel programming!) I didn’t give much attention on this until it was too late. I was trying my hardest to get pachube feeds to the game when I thought, “It’s going to take a lot of time to set this up. And I still don’t have any idea how to interpret the data into the game aside from changing the background. Maybe if the sensors just tweet me stuff they want to happen to the game…”
So I connected the game to twitter and the possibilities of the tweeting interaction began pouring as I code it. The game tweets, players tweet the game. And since I know that the game was only going to be played within the PCs of Biomodd, I can get away with this easily. It won’t flood Twitter’s bandwidth, players feel Makiling in the context of the game and the installation and there’s certainly the “Whoah, this has never been done before” factor.
The project is definitely my most challenging yet. I don’t want to conclude.
It is what is. 🙂