There’s Still Time to Celebrate Cinco de Mayo in Happy Island

Thu, May 6, 2010

Facebook, Social

It seems that most Facebook game developers understand the real world issues that may arise in a player’s life, inhibiting them from logging into their games each and everyday. This has been seen more times than can be counted with the extension of holiday celebrations, as one major example, that sees holiday-themed items being available to purchase long after the holiday has come and gone.

Such is the case with CrowdStar’s Happy Island and the Cinco de Mayo Pinata. Regardless of the fact that Cinco de Mayo was yesterday, users can still purchase this pinata, which serves as a sort of mystery box. Available for 24 Facebook Credits (around $2.50), users who purchase the pinata will be given one of 15 different items, each of which is valued at more than the pinata’s price. That is, each of the 15 prizes would be purchased through normal means for more than 24 Facebook credits, so you’re coming out ahead on the deal.

The kicker here is not knowing which item you’ll receive, and running the risk of receiving a duplicate item, should you decide to purchase more than one. Willing to take the chance at receiving something great? Head over to the game’s page and break one open for yourself! What did you get inside? Let us know in the comments!

Be Sociable, Share!

Related posts:

  1. Celebrate Cinco de Mayo in Pet Society
  2. Zynga Kicks Off a Cinco de Mayo Celebration in FarmVille
  3. Restaurant City Celebrates Cinco de Mayo in a Big Way With New Items
  4. Tiki Resort Continues the Cinco de Mayo Celebration
  5. Restaurant City Celebrates Cinco de Mayo With New Recipes
, ,

This post was written by:

- who has written 2533 posts on Frisky Mongoose.

Brandy is the Social Editor at Frisky Mongoose, focusing on the social side of the gaming world.

Contact the author


Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0