roles: User experience design & project management
Knote is a single player experiential game made for my advanced mechanics class. For this project we were meant to explore the idea of sound in games, trying to incorporate sound or music as a mechanic. Similar to games like Flow and Flower, we wanted to make an experiential game where there were no real goal to it, but had players enjoy the music.
The player controls a particle/shape and they interact with the different objects in the world. Different aspects of the environment and objects change depending on the feel/tempo/volume of the music.
The player controls a particle/shape and they interact with the different objects in the world. Different aspects of the environment and objects change depending on the feel/tempo/volume of the music.
Challenges
SONG CHOICE
The song that we chose to use for our game was an an orchestral piece (titles "Low Horizon") by Kai Engle. It was a free source song, and what we really liked about it was how powerful it felt, and we believed that it suited the feeling that we wanted for the game. However, the song was only about 3 minutes long, and we wanted the player to be able to play longer if they wished to. We had to listen to the song multiple times, figure out which parts would easily be able to loop, and looped it.
FLOW OF THE GAME
In our original visualization of the game, there were 4 parts/areas to the game. Similar to a rise and fall in a story arc, the player starts off calmly, begins to build up, the climax occurs, and then the player returns back to it's starting state. Each area corresponded with different parts of the song.
The song that we chose to use for our game was an an orchestral piece (titles "Low Horizon") by Kai Engle. It was a free source song, and what we really liked about it was how powerful it felt, and we believed that it suited the feeling that we wanted for the game. However, the song was only about 3 minutes long, and we wanted the player to be able to play longer if they wished to. We had to listen to the song multiple times, figure out which parts would easily be able to loop, and looped it.
FLOW OF THE GAME
In our original visualization of the game, there were 4 parts/areas to the game. Similar to a rise and fall in a story arc, the player starts off calmly, begins to build up, the climax occurs, and then the player returns back to it's starting state. Each area corresponded with different parts of the song.
