X

Worms 4: Mayhem Latest News - PC

Worms 4: Mayhem
Game Description:After the tactical RTS play of Worms Forts Under Siege, Worms 4: Mayhem is a return to the series' trademark gameplay and sees Team 17's core Worms design and development team regrouping for a 3D game of explosive annelid annihilation. With players controlling the worms in single player or 4-player team games, everyone's armed with a massive variety of wild weapons, as ingenious as they are incendiary. The worms' armoury of brilliantly conceived classic weapons return and is built on with even more devilish devices, including the Poison Arrow, Sentry Gun, Tail Nail and the Bovine Blitz, which unleashes a bombing raid of cows. Customize your worm's character in an all new Worms creator feature and unleash annelid annihilation across 25 single-player missions and 20 multiplayer maps.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Worms 4: Mayhem News

Displaying 1–1 of 1 articles

  • Worms Ultimate Mayhem Is A Little Bit Old, A Little Bit New

    You have to appreciate the charming simplicity of the gameplay in Worms: two warring factions of the slithery little beasties take turns launching a startling array of firepower across a map, until one group or the other has been wiped out. It's the reason the games continue to be so popular and also why fans are sure to be excited about Team...

    Posted July 29, 2011

    Worms Ultimate Mayhem Is A Little Bit Old, A Little Bit New

 


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>