X

ArchLord Screenshots and Images - PC

ArchLord
  • Publisher: Codemasters
  • Genre:RPG
  • Developer: NHN Games
  • Release Date:Oct 3, 2006
  • # of Players:1 player
  • ESRB:T - Teen (Blood, Mild Suggestive Themes, Violence)
  • Platforms:
Game Description:In this massively-multiplayer online game, ArchLord features an advanced player-vs-player combat system, utilizing sprawling free battle areas and special guild battlefields that enables players to battle in fearsome guild versus guild battles. With an ever-evolving storyline of conquest and betrayal, ArchLord presents an epic adventure in which players band together as they quest for the ancient relics of the Archons. Each relic bestows incredible power on those who possess it and when relics are combined they deliver ultimate mastery over the fundamental forces of creation for there can only be one Archlord! Every month, one player will take control of the world, and with it the opportunity to wreak havoc on their cowering enemies as the player gains control of supreme global Archlord powers!
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game
  • ArchLord Cinematic Trailer

    Posted: July 16, 2009

    1,921 Views | 04:06

 


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>