X

Worms 4: Mayhem Latest News - XBX

  • Publisher: Majesco
  • Genre:Strategy
  • Developer: Team17 Software
  • Release Date:Oct 4, 2005
  • # 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:The comic crawlers in Worms 4: Mayhem are lovable, customizable, and totally destroyable! The latest installment of the highly addictive Worms series lets you blow 'em up in five themed worlds: Jurassic, Camelot, Arabian, Construction, and Wild West. Pretty much everything you see in the expanded 3D environments can be obliterated. You've got plenty of weapons to help do it, including bazookas, homing missiles, poison arrows, grenades, banana bombs, and even sheep and old ladies. Twenty-five single-player missions go beyond the usual day-to-day business of destroying worms by challenging you to recover items or smash scenery. Multiplayer offers those same 25 missions plus 20 more maps to blow up.
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>