X

Rune Factory 2: A Fantasy Harvest Moon Screenshots and Images - DS

  • Publisher: Natsume
  • Genre:RPG
  • Developer: Natsume
  • Release Date:Nov 21, 2008
  • # of Players:1 player, 4 online
  • ESRB:E - Everyone (Mild Fantasy Violence,Mild Suggestive Themes,Use of Alcohol)
  • Platforms:
Game Description:The second installment in Harvest Moon's Rune Factory series comes with a big first: a story so large it spans two generations. Several years after the first Rune Factory, the Kingdom of Norad remains at peace. You'll play as Kyle, a mysterious figure who arrives at Alvarna Village just as whispers of a looming danger are beginning to spread. Build a life in the Village as you try investigate the rising threat. Run a farm, get to know the townsfolk, raise monsters to help on the farm, complete quests, find a wife, and start a family. Eventually, the story continues as you play through the eyes of your own child.
G4TV Rating
N/A
  • Avg User Rating
    (3 Ratings)
    4.7 / 5
  • Rate This Game

Rune Factory 2: A Fantasy Harvest Moon Screenshot & Image Galleries

  • Trailer - Rune Factory - A Fantasy Harvest Moon

    Posted: May 30, 2008

    4,175 Views | 01:41 | 1 Comment

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>