FreeAppADay for 03/30/10: Scribattle

Tue, Mar 30, 2010

iPhone, Mobile

As reported by the folks at FreeAppADay, today’s free app is Scribattle, from Rebisoft. Described by the developer as something along the lines of Space Invaders or Missile Command, Scribattle has the look of a pen and paper drawing that sees you controlling stick men at the bottom of the screen, as you try to defend yourself from wave after wave of creatures that are approaching from the top of the screen.

To fire at your enemies, you tap on a warrior of your choosing and gently flick in the direction you want him to shoot. The game’s multi-touch support allows you to fire with more than one stick man at a time, as you attempt to take out the game’s four different types of enemies. Gameplay is highly customizable, allowing you to choose from four different difficulty settings, and furthermore, change settings allowing you to play with or without shields on your men (shields are activated by holding your finger over your stick men), and with or without running into the Noodly Appendage, the game’s most challenging enemy.

There are 50 levels in Scribattle, but if you’d like to continue playing after clearing them all, you can recycle through the levels, that have now been made more difficult on your subsequent playthrough. Conversely, if you don’t make it through all 50, you can start a new game in the highest level that you have reached and continue from there.

Be Sociable, Share!

Related posts:

  1. FreeAppADay for 07/26/10: Stick Golf
  2. FreeAppADay for 08/09/10: Critical Wave
  3. FreeAppADay for 07/30/10: Zombie Shock
  4. FreeAppADay for 08/15/10: Streetball
  5. FreeAppADay for 04/06/10: Artifice
, , ,

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