X

Mario Party 6 Videos and Trailers - GC

  • Publisher: Nintendo
  • Genre:Party
  • Developer: Hudson Soft
  • Release Date:Dec 7, 2004
  • # of Players:4 players
  • ESRB:E - Everyone (Everyone)
  • Platforms:
Game Description:Note: Nintendo GameCube Mic can be used in some mini-games, however it is not required for gameplay. Microphone is not included with rental. Furious four-player Mario Party fun returns to the GameCube this season! The Sun and Moon are caught up in a feud over who is better, and Mario and the gang must settle the argument and restore some order to the cosmos. Party Mode features six fresh game boards, each with different objectives, and over 80 new mini-games to choose from. Depending on whether it is daytime or nighttime, game boards transform, characters come out of hiding, and mini-games change dramatically. All your favorite Mario characters will be returning, of course, with the addition of Toad and Koopa Kid this time around. You can even control the mini-game action with the sound of your voice using the GameCube Microphone!
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    4 / 5
  • Rate This Game

Mario Party 6 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>