Thursday, October 28, 2010
ChuChu Rocket!
ChuChu Rocket! was originally released for the Sega Dreamcast by Sega (with the game being developed by Sonic Team), and it has since been released for the Gameboy Advance and iOS as well. It is a single- and multi-player puzzle game with an unusual and unique form of gameplay, with the player placing arrows upon the playing field to direct mice to safety, while making them avoid the cats that may harm them.
Although it has a very simple idea behind it, ChuChu Rocket! is more complex than one might think. In the single-player puzzle mode, players are challenged to use a limited number of arrows (with pre-set directions) to keep the mice away from cats and lead them into the rocket ships placed on the level. Every mouse constantly walks forward, only changing direction when bumping into an object (in which case it turns around or goes around a corner, depending on the situation) or an arrow (in which case it moves in the direction the arrow points). The puzzles start out easy, but grow very difficult as more cats, walls, pits, and more are added into the mix, especially since the player cannot see how the mice will actually act till they are done placing their arrows. The multi-player mode is more hectic, with the players all placing their arrows (of which only 3 can be placed at a time, with old ones disappearing after a short time or if a 4th one is placed) during live gameplay and trying to drive the mice into their own rockets instead of their opponents. The game's online multi-player became so popular that the game was eventually given away with the Dreamcast in order to increase the console's sales.
The game's concept is, of course, very odd. However, it is also one that could have very easily been prototyped physically, at least for its single-player mode. The mice, as mentioned earlier, follow a simple set of rules and all interaction with the map happens before the mice move, so it is likely that the designers simply used a grid drawn on paper as a prototype of the map, with different paper tiles representing the mice, cats, arrows, pits, and walls. As long as the rules governing mouse and cat movement were followed correctly, they could have been manually moved through the board to see if the player had completed the puzzle correctly.
For the game's multi-player mode, a software prototype was probably required. It would have required too much work for players to manually place arrows while also moving every mouse on the board, so a software prototype could have been set up instead. It would have been focused on making sure the mechanics worked correctly, since if any of the mechanics did not work, the entire mode would be unplayable, either due to the increased difficulty that the mice moving too fast would cause, or the frustration a player would have with the mice if they didn't move as the player directed them to. Prototyping the game must have required carefully making sure everything worked as the designers needed it to, and it seems that they managed to pull it off.
Thursday, October 21, 2010
Castlevania: Symphony of the Night
Castlevania: Symphony of the Night is a 2D adventure game developed and published by Konami for the Playstation. The player controls the character Alucard, the song of Dracula, as he explores his father's castle in an attempt to become stronger and defeat him. The player can find a variety of items, weapons, and "relics" (which unlock new abilities) hidden throughout the castle, with the player being able to take a very non-linear path as to what order they discover things in, with the only exceptions being certain plot-related events.
It is interesting to note that Symphony of the Night is almost nothing like the games that came before it. Earlier Castlevania games took place on long levels that had several alternate paths which eventually lead back to the same main path, or opened up an alternate stage that then lead back to the same stage the player would have normally played. Symphony of the Night changes this entirely by introducing the concepts of an inventory, character stats, spells, health and magic upgrades, and more, as well as only having one "level"- the castle in its entirety. As mentioned earlier, Alucard can explore the castle's rooms in any order, bound only by his strength and the abilities the player has acquired. This new formula, alongside with the Metroid series, birthed an entire genre of games known as "Metroidvanias".
For such a radical departure from the main series of games, Symphony of the Night's designers must have thought very hard about what new ideas they wanted to add. They most likely wanted to place a focus on "exploration" and "freedom", if only because they can be said to be the core of the game. The player's ability to explore in the order they choose was an almost unthought of idea at the time, so the designers took a big risk in using it. Other big ideas the designers probably focused on are "allowing the player to use items whenever they want" and "giving the player the ability to change how they attack", as well as the idea of assigning each monster a certain amount of HP and having each weapon due a different amount of damage. These changes made the game more like an RPG than previous games, with killing monsters to level up and improve Alucard's stats becoming very important.
The thought that the designers of one game taking a risk led to the development of many other games is both strange and humbling. The importance of introducing new ideas into gaming is best shown through examples like Symphony of the Night: even the widest departures from what players consider normal can be great as long as they are implemented well.
Friday, October 15, 2010
Project Diva
(Image Courtesy of IGN)
Feedback in the game is shown in several ways. The first, of course, is the player's score. It goes up for each note the player hits, with the amount increasing varying based on the player's timing and how many notes that had hit in a row before that note. This score determines whether the player passes or fails the song, and what grade the player gets at the end, which is perhaps the most important form of feedback a new player can receive, along with the other information that is given to the player at the end of a song.
The player's success also depends on a meter at the bottom left corner of the screen. This meter, which goes up or down based on how well the player is doing, will end the game if it reaches the bottom. In order to continue to do well, the player must hit many notes in a row and build a combo. The number of notes in the player's current combo is shown after each note the player hits, and building a large one is especially important during certain sections of each song that can guarantee victory or failure depending on how the player does. During these portions, the player must do very well, because the score given to the player is given according to the formula "score=100*x", where x is the size of the combo the player currently has, with 50 being the highest it can go.
Finally, the player's progress is shown in the amount of items they unlock. Reaching certain goals (varying from getting a certain combo to reaching a certain score) for each song unlocks new costumes, songs, and pictures to look at. Some of these goals are very hard to reach, making beating them a clear sign of progress. If the player does well enough, they can even play as other characters, and equip costumes based on outfits from other games, something that fans of those games will find a true indicator of success.
Thursday, October 7, 2010
Cave Story
(Image courtesy of Aeon Genesis)
Cave Story is a single-player platformer game developed by Studio Pixel and translated by Aeon Genesis, which was originally released for the PC, with Wii and DSi ports created and retranslated by Nicalis.
Cave Story follows the actions of a robot named Quote who, after being awoken in what appears to be an underground cave, sets out an adventure. While the game starts with this as its relatively simple premise, its story is more complex than one would think, as it fits the dramatic arc of traditional storytelling.
The exposition of the story begins when Quote discovers a village filled with strange, bunny-like humanoid creatures called Mimigas. It is explained to him that a human girl named Sue who was turned into a Mimiga is being pursued by an evil man known only as the Doctor. His minions kidnap another Mimiga by accident, and when Sue is found, she is imprisoned as punishment for the trouble she caused the village. Quote decides to help her by finding and rescuing her brother, who is somewhere nearby the village.
The rising action starts soon after, when Quote finds Sue's brother Kazuma and their friend, Professor Booster. Through them, Quote is sent on missions in nearby areas, and the background of the story is slowly revealed to him. Quote is revealed to be a combat robot that was sent to these caves, which are in reality within a floating island, to fight the Mimigas. This is because the Mimigas become incredibly aggressive if they ingest a certain red flower, which the Doctor is trying to find in order to create a Mimiga army. Quote confronts the Doctor, but is sent to a maze deep within the island after he defeats the Doctor's minions.
After this point, Quote mainly tries to escape to the higher areas of the island, and this makes up the falling action of the game's story. Eventually, Quote and his allies make their way to the top of the island, where Quote finally gets a chance to battle the Doctor.
The resolution of the game's story can be slightly changed by how the player played the game, with picking certain options and performing certain difficult tasks giving the player a better ending. The player can also chose to leave the island, giving them a bad ending where the Doctor wins. If this is not chosen, Quote defeats the Doctor, and then fights the corrupted core of the island itself, before escaping with his allies. While not as extremely long or twisted as the stories of some games, Cave Story's story is certainly not as basic as its title would suggest.
Subscribe to:
Comments (Atom)