X

Kingdom Under Fire: Heroes Videos and Trailers - XBX

  • Publisher: Microsoft
  • Genre:RPG, Strategy
  • Developer: Phantagram
  • Release Date:Sep 21, 2005
  • # of Players:6 players
  • ESRB:M - Mature (Titles rated "Mature (M)" may be suitable for ages 17 and older. They may include more intense violence or language than products rated "Teen" as well as mature sexual themes.)
  • Platforms:
Game Description:Reestablish order in the Kingdom of Bersia and you'll go down in history in this prequel to the 2004 hit, Kingdom Under Fire: The Crusaders. Set five years before The Crusaders, Heroes follows seven new characters through 50 new campaigns in the war that will decide the fate of all mortals. Each character has new skills and a distinct tie to the original Kingdom Under Fire storyline. Vanquish enemies on improved, more-epic-than-ever battlefields. Choose from several training modes or behold the impressive power of Custom Game Mode, which allows you to create almost any type of mission imaginable. Team with or battle against fellow knights online with Xbox Live.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Kingdom Under Fire: Heroes Videos

Displaying 1–1 of 1 videos

 


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>