X

Baldur's Gate II: Throne of Bhaal Latest News - PC

Baldur's Gate II: Throne of Bhaal
  • Publisher: Interplay
  • Genre:RPG
  • Developer: BioWare
  • Release Date:Jun 22, 2001
  • # of Players:1 player
  • ESRB:T - Teen (Blood, Use of Alcohol and Tobacco, Violence)
  • Platforms:
Game Description:War wreaks havoc among the Bhaal Spawn, and as a Child of Bhaal, you too become embroiled in the conflict. The mysteries concerning your dark heritage require final answers, and the secrets of your hidden powers are soon to be unleashed. Your journey down the Sword Coast has finally lead you just south of Amn, to the country of Tethyr. It is here, on this final battlefield, that the victors shall rise above the vanquished. You are the Bhaal Spawn, and your ultimate destiny will be yours for the taking! In the expansion set to the award-winning Baldur's Gate II: Shadows of Amn continue your quest and conclude the epic saga. An exhilarating adventure unfolds when you explore new lands, battle fierce monsters and villains, and gain high-level abilities that bestow awesome powers.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Baldur's Gate II: Throne of Bhaal News

  • No results

 

 

 


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>