[This Gamasutra-exclusive postmortem covers the Eidos-published, Deadline Games-developed PSP exclusive Chili Con Carnage, which debuted in the U.S. in February 2007.]
I always find it difficult to write a post-mortem. There are so many experiences throughout the development of a game that it’s difficult to single out specific events or issues that you feel represent the essence of what went right and wrong. Nevertheless, looking back at the development of Chili Con Carnage there are definitely some lessons to be learned and remembered. I’d like to take this opportunity to share them with you.
The whole premise for making this game was that at the end of Total Overdose (released in fall 2005 for PS2, Xbox and PC) we felt we stood with a game that was fun and filled with good ideas but hadn’t managed to exploit the full potential of the core game mechanics. That, combined with the soon to be released Sony PSP, made us decide to make an adaptation of Total Overdose for the PSP. It was quite important for us that it was an adaptation and not a port as the game had to fit the handheld platform to achieve the greatest play experience.
We decided from the outset that we wanted to focus on the gameplay and create the best action game for the PSP. Furthermore we wanted the project to take no longer than a year so decisions were made very early about the ambitions with regards to new graphics, environments, story and music. In essence we felt that we could make a new and fresh game experience re-using many existing Total Overdose assets without compromising the quality or the goal of wanting to create the best action game on PSP.
So on we went, porting our proprietary technology to the PSP while developing the new game in our flexible PC development environment…
To be honest, there were a lot of things that went really well when developing this title. Somehow, most elements just seemed to “click” and it was pretty smooth sailing along the way. I’ll try and emphasize the areas I feel went best.
It’s a fairly clichéd point to always emphasize the team but we really had a good constellation of guys on the project. We had a new team leading the project with some Total Overdose “old timers” in supporting roles. This gave the necessary fresh look on the Chili feature set and made it easier to kill any darlings that the old team may have had.
Although the majority of the original Total Overdose team were working on their next project they were still so passionate about the old game that they were happy in assisting us whenever we had questions or problems and came with a lot of good advice and ideas that helped make Chili the game it is today.
Last but not least our own QA team was also great help when developing features providing us with feedback and statistics from copious amounts of play tests. I really urge anyone who has the possibility of using a QA department in the development process to do so.
The original Total Overdose team had so many great ideas and had so much drive to hone them that it made our jobs on Chili so much easier. We could basically cherry pick the best features and focus on them instead of trying to cram the entire PS2 game onto the PSP. This of course reduced the risk of having to invent a completely new game from scratch as we had our “feature prototype” in the already released game. You can say that we had the rare privilege of “finishing a game instead of shipping it”.
As you may or may not know Total Overdose and Chili Con Carnage both have their tongues firmly stuck in their cheeks and that just gave us so much leeway in how outrageous and silly we could get. We had a great time blue-skying the game and many design meetings felt more like attending a comedy performance than actually designing a game and it definitely made everyone feel really good about the game we were working on.
Our proprietary Kapow Engine is highly flexible and puts a lot of power in the hands of the designers and not just the programmers. Our tech department assured us that the existing feature set would be available on the PSP once they were done porting the tech. That meant we could basically start game development from day one on the PC instead of having to wait for certain features to be available.
This in turn meant that we had time to experiment and create many control and camera prototypes trying to home in on the optimal configuration for the “challenging” PSP controller layout. Combine that with the awesome work of our QA department and their play testers we had the perfect foundation to reach good if not excellent controls and camera on the PSP.
You could say that this is true for every game, but the fact that we could find a fairly well balanced control scheme very early in the development process meant that playing the game, testing it, iterating it, testing it again became so much more enjoyable for everyone and therefore the team was probably more likely to go through more iterations (thus achieving better results) than had the control scheme only been nailed down later in the project.
Our decision to create an adaptation and not a straight port of Total Overdose meant that our core feature set such as level design and sizes, enemy behaviors and core gameplay mechanics were all tuned for short play times, quick progression and instant gratification. The whole gameplay experience emerged into this snappy, frantic, instant fun type of affair as opposed to a lot of other games where transport, story and pace all work against the action principle and just slow things down.
It’s a format that I’m happy to see more and more PSP games adopting. That means that our decisions were right at a time where ports to the PSP were more common than new games or adaptations.
Everybody from tech guys, game programmers, level designers, graphic artists, animators and the sound designer were very passionate about the game and where we were taking it. On top of that the leads were very good at structuring the work load for their respective teams and that combined just gave a lot of confidence in the direction, scope and schedule.
My lead artist told me that he had clocked a total of 50 man-hours of overtime for his team on the project. The scenario was the same for all the other crafts groups and I’m happy to say that we were really good at scoping our ambitions and adjust deliverables to minimize the amount of overtime needed on the project instead of vice versa. The next goal must be to reach zero overtime.
As a funny side note I can tell you that the team was so dedicated that once when I came back from vacation they had made an entirely Danish version of the game, complete with voiceovers and whatnot, all in their own time. They had had so much fun doing it that the whole experience was a great morale booster. Unfortunately the Danish version didn’t make it into the final game as the QA time needed wasn’t scheduled and budgeted for (we can thank the Hot Coffee scandal for ruining impulsive easter eggs forever).