Harry Potter and the Deathly Hallows Part 2 (Xbox 360, PlayStation 3, Wii, DS, PC)
Developer: EA Bright Light
Publisher: Electronic Arts
To be released: July 12, 2011
There are quite a few other similarities between this game and Gears of War. For example, in Harry Potter, you lead a team of grizzled high school veterans against hordes of Death Eaters. In Gears, you lead a team of grizzly military types against evil aliens. Your lead character in Harry Potter has a scar on his face as does Marcus Phoenix of Gears. They both like making big explosions and running around with their friends blowing stuff up too.
The team says that they have addressed what the fans were asking for from the previous version of Deathly Hallows, such as being able to play as other characters in the story. During the demonstration, Professor McGonagall was used to fight off one of the giant bosses in the game. They also simplified the control scheme. Each spell in Harry's arsenal is mapped to a button on the controller and you simply pull the R trigger on the controller to cast whichever spell is equipped.
There is quite a bit of strategy in the way that you will have to defeat your enemies. Certain spells are just for defeating your enemy's shields and other spells are for dealing damage. You will have to find the right method of knowing which spell is going to be needed to take out the bad guys. Later in the game, you will also get the Apparate spell which will allow Harry to teleport to nearby cover in case of a surprise attack which seemed to happen often.
This game is a great starting point for kids whose parents will not let them have the Gears experience or if they are just Harry Potter fans in general. Either way, it is definitely a game that can be enjoyed by all. If you really want to spoil this game, there is a movie that will be coming out on Friday based on the exact same story. You should watch it. It's a big deal, apparently. Photo Gallery: (4 images)
Click to zoom - browse by swipe, or use arrow keys
can cause it. You can fix it by adding *.disqus.com to your whitelists.