X

Final Fantasy: Crystal Chronicles Videos and Trailers - GC

  • Publisher: Nintendo
  • Genre:RPG
  • Developer:
  • Release Date:Feb 10, 2004
  • # of Players:4 players
  • ESRB:T - Teen (Titles rated "Teen (T)" may be suitable for ages 13 and older, and may contain violent content, mild, or strong language, and/or suggestive themes.)
  • Platforms:
Game Description:SPECIAL NOTE: For multiplayer gameplay, each player must use a Game Boy Advance system and Game Link cable. The GBA screen will display important information unique to each player, allowing for advanced multiplayer action.Square Enix brings us Crystal Chronicles, a Final Fantasy adventure with a new otherworldly look and innovative co-operative gameplay. In a world ravaged by a poisonous cloud, your people depend on a protective crystal that needs Mirula Droplets to sustain its healing energy. But these crystal droplets can only be found in a far away dungeon deep under the earth. As part of the Crystal Caravan you will journey across dangerous lands, fight fell monsters, and brave a dark underworld. Crystal Chronicles supports single-player and multiplayer gameplay.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Final Fantasy: Crystal Chronicles 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>