Mario Super Sluggers Screenshots and Images - Wii

  • Publisher: Nintendo
  • Genre:Action, Sports
  • Developer:
  • Release Date:Aug 28, 2008
  • # of Players:1 player
  • ESRB:E - Everyone (Comic Mischief)
  • Platforms:
Game Description:Root, root, root for Mario Super Sluggers!  The follow-up to the GameCube hit makes its debut on Wii. Choose one of 12 Mushroom Kingdom all-stars as captain, including Mario, Luigi, Peach, Daisy, Donkey Kong, Waluigi, and Wario and lead your team to victory.  A cast of 40 supporting characters, including Toad, Goomba, Hammer Bros., and Shy Guy, will assist you in your quest for diamond domination. Take to the field with friends in Multiplayer Mode or play baseball inspired mini-games in Party Mode.  Veterans and rookies alike can have a good time with a choice of different control schemes that level the playing field.
G4TV Rating
  • Avg User Rating
    (2 Ratings)
    4 / 5
  • Rate This Game
  • X-List: Top 5 Hero/Villain Combos In Gaming

    Posted: April 18, 2011

    30,952 Views | 01:06

  • Videogame Deathmatch 2011: Best Franchise

    Posted: March 28, 2011

    13,878 Views | 03:35

  • Mario Super Sluggers Review

    Posted: September 11, 2008

    12,826 Views | 02:04 | 5 Comments

  • Mario Super Sluggers Gameplay Footage

    Posted: July 17, 2008

    1,024 Views | 01:27

  • X-Play Gaming Update 04.11.08

    Posted: April 11, 2008

    4,031 Views | 01:33 | 1 Comment


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 -->

        <customErrors mode="Off"/>

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 -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>