X

Viva Pinata: Party Animals Latest News - Xbox 360

  • Publisher: Microsoft
  • Genre:
  • Developer:
  • Release Date:Oct 31, 2007
  • # of Players:1 player, 4 online
  • ESRB:E - Everyone (Cartoon Violence,Comic Mischief)
  • Platforms:
Game Description:Those crazy Piñatas are back, and it's up to you to entice them to come into your garden! You are in control as you determine the fate of all your favorite characters, including Fergy Fudgehog, Paulie Pretztail, Franklin Fizzlybear, and Hudson Horstachio. More than 40 different mini-games and a dozen different foot races let you compete against one another. Make sure you collect the special bonuses and candy, which hide out in exotic and dangerous locations! Join with friends online to share with other piñata lovers from all over the world, or play with three friends all on the same console!
G4TV Rating
N/A
  • Avg User Rating
    (2 Ratings)
    3 / 5
  • Rate This Game

Viva Pinata: Party Animals News

Displaying 1–1 of 1 articles

  • Rare To Restructure

    Venerable game developers Rare (Banjo Kazooie, Viva Piñata, Xbox LIVE Avatars) are facing some tough times due to the sluggish economy. Microsoft is reviewing Rare and plans to restructure it. It's a move that could lead to job cuts. Rare plans to focus on three areas as specified by Microsoft. It will look at expanding the existing 360...

    Posted February 17, 2009| 45 Comments

    Rare To Restructure

 


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>