X

Pac-Man World 2 Latest News - GC

  • Publisher: Namco
  • Genre:Platformer
  • Developer: Namco
  • Release Date:Mar 12, 2002
  • # of Players:1 player
  • ESRB:E - Everyone (Everyone)
  • Platforms:
Game Description: Help Pac-Man get back the Golden Fruits from Spooky and the rest of those thieving ghosts. In this 3D platform game, Pac-Man must fight his way through five fantastical worlds and 25 levels. When you're done with the full game, there's an extra added bonus: full versions of four 1980s classic Pac-Man games (Pac-Man, Ms. Pac-Man, Pac-Attack, and Pac-Mania)!
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Pac-Man World 2 News

Displaying 1–1 of 1 articles

  • A 420 Treat: Top Five Food-Related Video Games

    In honor of 4.20, TheFeed is proud to present a list of the top five food-related games ever made in video game history. Enjoy it with some raw cookie dough and a huge glass of milk. Pac-man-- Old-school games are really heavy on creatures eating one another, a theme that isn’t explored in modern games nearly enough, and 1983’s...

    Posted April 20, 2010

    A 420 Treat: Top Five Food-Related Video Games
  • 'Pac-Man vs.' and 'Pac-Man World 2' Bundle Review

    Posted: February 6, 2004

    767 Views | 02:49

 


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>