Ninja Gaiden II on NES is wicked hard PDF Print E-mail
User Rating: / 0
PoorBest 
Gaming - NES
Written by Jimbag   
Saturday, 28 November 2009 17:07

Lately, I have been consumed by a Nintendo Entertainment System game collecting fix.  I have been going throw my old games and picking up some new ones by way of eBay.  Dusting them off, cleaning off some grim and NOT blowing in them.  Never liked to blow into the games.  If I ever do, I always put a cotton filter over it...cotton filter being my t-shirt that I am wearing.

Anyway...Ninja Gaiden II: The Dark Sword of Chaos on the NES is completely ridiculous.  B-Rye was over and I was hoping that he would want to play some Mega Man 2 or some TMNT 2, but no.  He picked Ninja Gaiden 2 off of the shelf.  I couldn't remember getting past the level where the wind changes directions on you as a kid.  Anyway, he started playing it and did pretty well.  Handled the controller off to me and I hit start and apparently you have continues...I think it is unlimited continues.  So we just kept trading the controller off.  I will admit, B-Rye did must of the grunt work.  I beat one of the bosses by doing a cheap move.  After a lot of close boss battles that went in our favor, we were all the way to 7-2 (7-5 is the final boss).  I was ass terrible at this level.  Took me a lot of tries to get the timing down right on where the enemies come from.  But this was our doom.  You can get all the way to the first boss on your first guy of the continue and if you die at the boss, it does not send you back to the last checkpoint (there are 2 checkpoints before the boss).  It sends you back to the beginning of the entire level so that you can get violated by all the ninja psychopaths and crazed green birds all over again.  Needless to say, after a couple of hours victory was not ours and we did not get to see the glorious final cut scenes.  We got owned. 'nuff said.




Reddit! Del.icio.us! Mixx! Free and Open Source Software News Google! Live! Facebook! StumbleUpon! TwitThis Joomla Free PHP
 
 

Tweets

An error occurred

Oops, an error seems to have occurred. We're sorry for any inconvenience this might have caused. If the error persists, feel free to tell us about it.

Twitter could not be reached, the server response code was: 401