X

Record of Agarest War Latest News - Xbox 360

  • Publisher: Aksys
  • Genre:RPG
  • Developer:
  • Release Date:Apr 29, 2010
  • # of Players:1 player
  • ESRB:T - Teen (Alcohol Reference,Mild Fantasy Violence,Mild Language,Partial Nudity,Suggestive Themes)
  • Platforms:
G4TV Rating
N/A
  • Avg User Rating
    (4 Ratings)
    3.8 / 5
  • Rate This Game

Record of Agarest War News

Displaying 1–1 of 1 articles

  • Record of Agarest War Limited Edition Creeps Me Out

    Until this morning, Record of Agarest War was totally off my game radar. The Japanese strategy role-playing game hasn't been released in the States, and, quite honestly, it has the least memorable title I've ever heard. But it does, apparently, have one unique thing going for it: Along with the strategy, players can engage in a dating sim with...

    Posted January 27, 2010

    Record of Agarest War Limited Edition Creeps Me Out
  • X-List: Top 5 Most Embarrassing Games

    Posted: March 30, 2011

    37,669 Views | 01:35

  • Record of Agarest War Gameplay Trailer

    Posted: April 6, 2010

    3,292 Views | 02:13

  • Record of Agarest War The Really Naughty Limited Edition

    Posted: January 27, 2010

    9,913 Views | 01:15

 


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>