Cut the vegetables in rhythm and make the best ratatouille France has ever known! Help Carlo Bonissima, one of the best French cooks, cut vegetables in rhythm in order to create the best ratatouille of the world! Choose the amount and category of vegetables you need and start making the best rhythmic cuisine you've ever seen!
Coupe Et Touille is an arcade rhythm game. The player's objective is to simply get the highest score by cutting at the right time the vegetables that appear on the screen. Given that it's a mobile game, it was mandatory to let the players experience the full game loop in a short amount of time. Thus, the game gets more or less difficult and long depending on the amount of vegetables the player decides to cut.
The game was made in pixel art. This choice was initially made because of the time constraint we gave ourselves. Furthermore, working with pixel art helped our game designer work relatively fast.
The objective was to create a scene with dim warm lights in order to give a chill and tranquil atmosphere to the kitchen. When it comes to the player, he was created using saturated and bright colors in order to direct the player's eye to him.
Coupe Et Touille was created for a challenge that we gave ourselves. In this challenge, every member had to create a prototype or a project in 2 week, while following a random theme. The theme that we got for those 2 weeks was "France - Cook". This explains the choices the game designer made about the creation of the game.
Coupe Et Touille represents our first video game production. In the future, we would like to create more video game projects.
When it comes to Coupe Et Touille, we've had a lot of constructive criticism et we are planning to add new features to the game later on.
Just like the rest of the game, the music of Coupe Et Touille was created by the game designer of Kaiso Studio. The music was created using the free program Bosca Ceoil, which is used by a lot of people who make retro game music.
Coupe Et Touille was developed on Unity, with the usage of C#. We tried to create solid and flexible systems in order to limit bugs and loopholes. We mainly used the Observer design pattern, which means using Events and Event Triggers as much as possible, in order to decrease the use of the Update method.