KITCHEN FRENZY
Released july 2004
ENJMIN End year project
Creative director
- Work
- Kitchen Frenzy
- Story of the making of
So, here’s the story behind the creation of Kitchen Frenzy. I could have written a proper postmortem, but I’d rather tell the story chronologically as it happened.
To sum it up, Kitchen Frenzy was a game concept we developed during the DESS Video Game School in Angoulême.
Team Members:
Cedric Barthez – Producer, Creative Director, Animator
Emeric Thoa – Game Designer and Ergonomics Designer
Alexandre Jully – Game Designer
Pedro Alessio – Graphic Designer
Christophe Panattoni – Lead Programmer
Nicolas Magnesse – Programmer
Xavier Collet – Sound & Music Designer
Website: https://www.cedricbarthez.fr/kitchenfrenzy
The Team
It all started in early January 2004. We had just arrived for the first classes of the DESS Video Game program when we decided (“we” meaning the whole class) to create teams so everyone could start working.
Our team came together in a pretty unusual way. Since I was a Game Designer and had quickly become friends with Alexandre, another GD, we decided to form a group with Pedro, my roommate. Later on, Emeric, Xavier, Nico, and Christophe joined us somewhat randomly because they didn’t really know where to go. Roger also joined us for a while, but left almost a month later because he was more interested in the western-themed project.
Shaman
We started holding meetings to get to know each other better and think about what kind of game we wanted to make. We brainstormed around the mandatory theme: “Heatwave.” The first idea was naturally to make a game set in a hot environment. Then, pretty quickly, we started thinking about shamans, a subject Xavier was particularly passionate about.
The Game Designers got to work and came up with the idea of a pacifist shaman who fights by taking possession of his enemies’ shadows. The idea was pretty good, the universe was interesting, and the team was almost fully convinced. I even made a storyboard detailing the game’s combat system.
Then we met our mentor… and he really wasn’t inspired by it. So we started questioning the concept. The discussion with the mentor mainly revealed that some members of the group weren’t actually very interested in the project. We decided to take two weeks to think things over.
Note: At that time, our mentor was Renaud Boclet.
The Idea!
During those weeks of reflection, we thought about all sorts of ridiculous ideas (including a “shaman beaver” concept). Then one day, while talking in class with Alex, we started discussing Le Petit Chef, a Japanese cartoon from the 80s. I had never seen it, but I loved the idea of over-the-top cooking duels.
Later, I talked about it with Emeric, who remembered the show, and we started joking around imagining a duel where cooks could throw things at each other’s faces. I even imagined a first level where they had to shop in a supermarket using physics-based shopping carts. In my mind, it was basically Mario Kart with shopping carts.
Anyway, the idea of a cooking duel slowly started growing in our minds.
The Vote
At the beginning of February, we attended Imagina. One of the things we learned there was that we were changing mentors. Our new mentor was Alexandre Topol, a teacher from the CNAM. I won’t talk much about him afterward because we only met him two or three times in total. At least he had the merit of letting us work peacefully, unlike some mentors who were far more intrusive than helpful (I won’t name names).
When we came back from Imagina, we decided it was time to settle on a concept. We held a meeting where everyone presented the game ideas they had during the previous weeks, and then we voted.
There was the original shaman idea, a concept about a character traveling on a magical cloud, a sled racing game, and the cooking game idea. In the end, we chose the cooking game, with Alex, Emeric, Pedro, and myself voting for it as our top choice.
Deep down, I knew we had something strong, simple, and truly original. Looking back, though, I think the concept was so weird and unconventional that we probably would have chosen another project if I hadn’t been with this particular group.
Still, everything remained to be done. At that point, all we really had was the idea of a cooking competition where chefs could throw things at each other.
The Work
We started working on the game design around February 10th. Before reaching the final concept, we went through several gameplay systems.
The first version was rhythm and music-based. Players had to cook in rhythm, and the better they performed rhythmic patterns, the faster the tempo became. The system caused many problems, mostly related to the interface. Personally, I didn’t want a Dance Dance Revolution-style interface cluttering the screen, so we abandoned the idea.
One of our earliest goals was also to include a lot of strategy. Players would choose the order in which to prepare and cook ingredients depending on preparation and cooking times, combined with player dexterity. Unfortunately, communicating all this information to the player would have required a very intrusive interface. We considered integrating it directly into the 3D environment using colors and visual cues, but in the end we wanted something fun and arcade-oriented.
That’s how we arrived at the final system: ingredients appear one after another in front of the chef, and the player must prepare them as quickly as possible. Each ingredient offers different gameplay mechanics based on reflexes, dexterity, rhythm, and so on. On top of that, players can earn Mario Kart-style bonuses to slow down their opponent.
Another important point for us was food quality. We didn’t want success to rely only on speed. So we added a quality factor for each ingredient. The final score depends both on speed and preparation quality (making fewer mistakes, etc.).
From the start, the game was centered around a duel between chefs. There was a long debate about whether the game should use split-screen or not. Gameplay—and I—ultimately imposed split-screen.
A quick word about the platform: it was obvious the game had to be made for consoles. We couldn’t picture this kind of game for PC players, and honestly it’s just more fun to play with a controller.
By the end of March, all these gameplay questions had been solved.
The Title
The first real title was Kooking. Alex had originally named the shaman project K Project, with the “K” coming from the beginning of the French word Canicule (Heatwave).
Later, I named the cooking project Cooking Party, then Kooking Project, reusing Alex’s “K” idea. Then, I think it was Xavier who pointed out that we could make a pun with “Kooking”… “Koo King.” We had our title!
Well, not exactly, because “Koo” apparently means “asshole” in Brazil, so we changed it to Kook King. We should also thank Gaetan, who explained to us that a good pun only works if both parts are actual words. Fascinating, right?
The Girls
One thing that was great about the DESS was its organization. The first three months were spent in Angoulême (January to March), then during April and May everyone was scattered across different cities depending on their specialty.
Game Design and Art students went to La Rochelle, Ergonomics students to Poitiers, and Programming and Sound Design students to Paris.
As a Game Design student, you can’t imagine how exciting it was to study in La Rochelle… especially during near-summer weather on a campus full of female students…
Losing Contact
Unfortunately, this happened right when we were supposed to enter production, with the programmers in Paris and the artist in La Rochelle. So things started looking pretty bad regarding team management and project progress.
We all had trouble communicating by email, and the less motivated people gradually lost interest. I knew that was going to happen, so I tried to prevent it by constantly sending emails to motivate everyone and show that I was still working hard myself.
In the end, the core team worked as hard as possible, and even though we fell seriously behind schedule, we still managed to move forward.
On my side, I spent the entire month of April finishing an advanced version of the Game Design document, including appendices and all that stuff. The Lead Programmer did some tests with RenderWare and created a C++ framework for the project.
At the end of March, I had quickly modeled two tables and two chefs so he could program split-screen and camera movement systems—which he apparently did with ridiculous ease.
The Title (Again)
Eventually, we changed the title again. We went from Kooking to Kitchen Chaos, and finally to Kitchen Frenzy. “Chaos” sounded too much like total mess, while “Frenzy” sounded more energetic and fitting.
Compared to Kook King, Kitchen Frenzy had a lot more personality. You could already tell the game would be a blast to play.
Note: Thanks to Renaud and Clément Merville for the help.
Placeholders!
At the beginning of May, I started to panic. The artist was seriously behind schedule on the character models (at least two weeks late), and the Lead Programmer needed animated characters to begin implementing gameplay systems.
In the meantime, I had created a complete storyboard for the demo’s mini-games and gameplay flow so the Lead Programmer could implement exactly what I wanted.
So I stepped in and spent two weeks doing tests alongside the programmer. I modeled placeholder characters, animated them, and sent them over so he could test animation blending systems. We also wanted the chefs to hold objects and switch between them dynamically, so we tested all of that too.
By the end of May, we had solved all those integration problems.
Production
At the beginning of June, we all returned to Angoulême to finish the demo. Here’s where we stood at that point:
The Lead Programmer arrived with a playable demo version featuring all the mini-games, but with placeholder characters, placeholder animations, placeholder environments, and no interface at all. There was debug text everywhere on screen, and we played the game like that. He had even programmed AI opponents :)
Xavier had run into many problems during the previous two months (viruses, etc.) and had only completed the menu music. Still, he came with a lot of sound effects.
He also couldn’t really work in Angoulême because the computers provided by the school were far too weak for composing music, and most of his equipment remained in Paris. His plan was to travel back and forth between Paris and Angoulême to compose and bring us the files we needed.
To be honest, I never really understood how he worked. What I do know is that whenever we gave him a deadline, he delivered on time. So I stopped asking questions.
Pedro still hadn’t fully completed the character models and was about to start skinning them, if I remember correctly. No environments or menus had been made yet, although the logo was already done.
As for me, Alex and I had finished versions of the Game Design, Prototype, and Project Management documents, which Emeric later polished at the end of June for the final submission.
Emeric had finished all his ergonomics assignments and was fully ready to work :)
But I’m sure you’re wondering if I forgot someone… Yep, the second programmer, from whom we had heard absolutely nothing for two months. Needless to say, he hadn’t done anything. But it wasn’t the time for arguments, so we simply got to work.
I won’t go into every detail of June, but we worked iteratively in roughly this order:
* integration of final character models with first-pass animations and sounds
* integration of a first interface version
* integration of gameplay objects (knife, meat, cabbage, etc.)
* integration of the environment, final animations, and music
* integration of camera movements, audience animations, and crowd sounds
* integration of menus and the second interface version
* integration of bonuses
* debugging and all sorts of fixes
As for task sharing:
* I created the chef animations, the in-game interface, the intro camera movements, some 3D objects, and various small elements.
* Emeric created the Flash menus, colored the characters, and corrected the documents.
* Alex worked on the trailer storyboard.
* Pedro modeled the characters, the environment, some 3D objects, designed the menu characters and crowd, handled the trailer visuals, and edited the trailer.
* Xavier composed the music, created the sound effects, crowd noises, and trailer audio editing.
* Christophe programmed everything except the sound and menus.
* Nico integrated the menus and sounds.
We also spent a huge amount of time on gameplay testing, asking the Lead Programmer to tweak balancing almost every day.
In the end, production went relatively smoothly. We only encountered a few technical problems, which we solved fairly quickly with help from other teams in the class.
The Presentation
At the beginning of July, we presented the trailer and demo in front of a half-empty amphitheater in the beautiful National Comic Art Center building.
The audience mainly consisted of DESS teachers, mentors, and professionals outside the video game industry. Well… Nicolas Gaume was there too. He had actually been pretty harsh toward the previous groups (we presented last), so when we reached the “Any questions?” moment, we expected to get destroyed.
Instead, he simply said: “In any case, congratulations!”
And believe me, we were incredibly proud.
He also invited us to present the game at Ubisoft in mid-July. The meeting itself didn’t really lead anywhere (and honestly wasn’t that interesting), but that wasn’t really the point.
The End?
In conclusion, I don’t think we ever could have reached that level of quality for the demo if our team members hadn’t worn multiple hats.
We were also smart enough to choose a technically manageable game style (no collision management, for example) that could easily be demonstrated in three minutes. That allowed us to focus on the little details that make all the difference: camera movements, intro sequences, presentation polish, and so on.
Another key element was the team’s motivation. Everyone was motivated because we knew we were making something genuinely fun, original, and good. Team motivation is probably the single most important thing to consider during production. We felt like we were creating something special, and that’s what pushed us forward.
The final step was the website, which I created at the end of August.
Now we’ll try to talk about the game everywhere we can. You never know… hope keeps you alive.
Download the demo and let us know what you think. The computer opponent may be a bit too strong, but with enough practice, it can definitely be beaten.