X

Grim Fandango Videos and Trailers - PC

Grim Fandango
  • Publisher: LucasArts
  • Genre:Adventure
  • Developer: LucasArts
  • Release Date:Nov 2, 1998
  • # of Players:1 player
  • ESRB:T - Teen (Animated Violence, Suggestive Themes, Use of Alcohol and Tobacco)
  • Platforms:
Game Description:Adventure game with a unique "Dia de los Muertos" look, from the mind of Tim Schafer. You play Manny Calavera, a mid-level worker at the Department of Death (the DOD) who's trying to work off his sins in life so that he can get to his final reward. As a reaper, Manny frees incoming souls from their shrouds, finds out what kind of underworld travel packages their goodness in life has earned them, and then sends them on their way. Unfortunately, business hasn't been very good for Manny of late. As the game begins, Calavera is told that he must sell a premium travel package to a soul or lose his job. In his search, Manny uncovers a hideous plot, a beautiful woman, and a crew of loyal friends (not necessarily in that order). The world is a rich one, complete with its own laws, its own personality types, and landscapes. The game takes place in four parts.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Grim Fandango Videos

Displaying 1–2 of 2 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>