1 vs 1 Competitive Gameplay | Direct Interaction with Game Objects | Playtesting on an early Prototype |
---|---|---|
Close-up Player Character | Playtesting and Feedback Evaluation | Playtesting |
Feedback Evaluation | @ GameSpace 2016 Exhibition, University of Applied Sciences |
RIPIT
RIPIT is a competitive multiplayer game. Two players control frogs in a pond by positioning analog pieces on the game board. Every few seconds, the frogs charge and stick out their tongues. Both players try to redirect their frogs' tongues to hit their opponents. The first player to hit their opponent six times wins the game.
PROJECT INFORMATION
Project Duration: 3 weeks
Production Date: 2015
Team Size: 3 people
Platform / Engine: PC, Unity 3D
Project Task: Hybrid Game - Design a playable game prototype that combines analogue and digital elements.
MY PART
Concept, Animation, Sound
I worked on the game concept and realisation of the prototype construction. Further more I created the music and feedback sounds of the game and several animations of the character.
WORKFLOW
Early on we thought about different ways to realize a game concept that combines analog and digital components. Detaching ourselves from the classic gamepad-controlled prototype, we instead created a possibility for the player to immerse directly into the game, by displaying the board on a surface and creating interactable pieces that indirectly affect the movement of the character.
Game Concept Illustration
Test Construction of the Game
The game construction consists of a semi-transparent pane which is the screen for the projector which is attached to a scaffold. Located below the pane, a camera traces the object movements produced by the players. To help the camera identify the objects, we added a light under the pane.
We managed to arrange all components successfully and began working on a setting for the game. Our goal was to create something funny and unique which translates the mechanics of the game into actions. Due to the limited amount of time, we settled for a pond setting, in which the main gameplay element would be the protruding frog tongues. Our artist Sheng designed simple and recognizable game assets and player characters appropriate for the low-resolution projector.
Player Characters by Team Member Sheng Chen
Screenshot - Gameplay
Player Characters by Team Member Sheng Chen
Assembling of Game Parts - Setting Up the Construction
Workplace - Time Schedule, Mood Board, Game Evaluations
Assembling of Game Parts - Setting Up the Construction
Satisfied with the setting, I began working on the frog animations by roughly planning out each animation time. Together with our programmer Josia, I coordinated the pace so that the animations would be fitting for each game interval.
After some sketches, we decided to use sprite animation for the movement, as it would reduce the workload. Since our frogs only differ in color, the finished sprite sheet for one player could easily be recolored to fit the other. Through this procedure, we produced several animations in a short amount of time.
Scetch for Swimming Animation
Sprite Sheet Swimming Frog / Program: Adobe Photoshop
Scetch for Swimming Animation
Creating simple Background Music / Program: Ableton Live
Construction of Feedback Sounds / Program: Audacity
Creating simple Background Music / Program: Ableton Live
After the animations were finished I had time left to create feedback sounds. After listing all the needed sounds and searching for suitable ones, I edited and combined them. My goal was to create funny and cute sounds that accompany the animations a mechanics. To intensify this effect, I created a simple and recognizable background melody.
SUMMARY
RIPIT is one of two game jam projects, created in 2015. Technical realization was more important than designing an outstanding interface or character. I gained my first experience with augmented reality and was surprised at how much fun a simple game mechanic could be.
Due to the three-week limitation, we had to make priorities and clearly assign tasks and responsibilities. I generated a simple time schedule managing the tasks of the team members and documented our decisions and work progress in a wiki.