Team Meat is Not On Team Freemium

Mon, May 7, 2012

Android, Arcade, Industry, Mobile

Freemium games may not be a business plan that’s for everybody, but it’s definitely not a plan that works for Edmund McMillen of Team Meat — they of the epic carnage-driven platformer that is Super Meat Boy. The Meating folks are working on a mobile version of SMB, and would like to let the world know that the mobile edition will most certainly not be free-to-play.

From the Team Meat Blog:

There is an on going theme these days to use a very basic video game shell and hang a “power up carrot” in front of the player. the player sees this carrot, and wants it! all the player needs to do is a few very rudimentary repetitious actions to attain it, once they get to it, another drops down and asks them to do more… but then the catch… instead of achieving these “goals” by running on the tread mill, you can instead just pay a single dollar and you instantly get to your goal! better yet pay 10 and unlock all your goals without even having to ever play the game!

words can not express how fucking wrong and horrible this is, for games, for gamers and for the platform as a whole… this business tactic is a slap in the face to actual game design and embodies everything that is wrong with the mobile/casual video game scene.

Mind you, if this philosophy doesn’t work out, they can just try again, and again, and again, and again, and see all of the prior attempts during the replay.

Be Sociable, Share!

Related posts:

  1. Fantasy Warrior Legends is Digital Chocolate’s First “Freemium” Game
  2. Feed Your Customers Dinosaur Meat in Cafe World
  3. Mario Marathon Team Gearing Up for Another Year
  4. RockYou Expands Team and Announces New Key Hires
  5. N Squared: Netflix & Nintendo’s Wii Team Up
, , , , , ,

This post was written by:

- who has written 1010 posts on Frisky Mongoose.


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