X

EverQuest II: The Bloodline Chronicles Screenshots and Images - PC

EverQuest II: The Bloodline Chronicles
Game Description:The first of a series of digital download Adventure Packs, each specifically designed to give players countless hours of new content in a rich, story-based realm located beneath the surface of Norrath. The Bloodline Chronicles takes you deep into the mysterious caverns beneath Nektulos Forest to investigate the source of strange happenings in the land of Norrath. Battle the denizens of the underworld to discover the dark secrets of the Tombs of Night - and enter, if you dare, the Crypt of T'Haen to confront the legendary lost lord of the undead. Content in The Bloodline Chronicles is geared towards level 30-45 players, however all players will be given access to one zone -- the Tombs of Night -- whether or not they choose to purchase the Adventure Pack.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game
  • EverQuest II "SOEmote" Launch Trailer

    Posted: August 9, 2012

    1,766 Views | 02:13

  • The MMO Report: Thursday, February 2nd

    Posted: February 2, 2012

    47,952 Views | 07:00

  • The MMO Report: Thursday, November 17th

    Posted: November 17, 2011

    19,271 Views | 07:40

  • The MMO Report: SOE Fan Faire Special

    Posted: July 21, 2011

    10,883 Views | 09:12

  • FanFare 2011 Costume Contest Video

    Posted: July 14, 2011

    4,432 Views | 03:22

 


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>