PacMath

Introduction

PacMath is an educational game based off the well known 80's arcade game PacMan. Using the original game concept PacMath will add fourth grade level math to the fun and exciting game of PacMan in order to make learning fun. The game will provide the student with different problems and in order to solve the problem correctly the student will have to eat the ghost with the correct answer.

Objective

The objective of this project is to incorporate the teachings of fourth grade mathematics to students through PacMath, a fun, interactive, mathematical game based on the 1980's PacMan.

Game Elements

• Sprites
  • Names and maybe their picture

How It Works

• One Player
• Board Setup like the Original PacMan (one Maze to start off)
• If the player eats a Power Pellet (4 per level)
  • Question Appears (4 per level -> 1 per Power Pellet)
  • After the four Power Pellets have been eaten and answer correctly a new 'level' (so to speak) begins
  • Player has to eat the Ghost with the correct answer (answers will be displayed on the ghosts throughout the entire 'level'
  • If the player eats the wrong answer they DIE!!!
  • If the player eats 100 (may change) regular pellets they gain a life
• Questions
  • Some default ones to start off with (come with the activity)
  • GUI/Prompt for the teacher to input their own questions, saves as an XML (the activity will load the file)
  • The answer will have a digit limit (thinking 3 digits)

Code Structure Plan

• Questions (default question list provided)
• Maze (single maze to start)
• Player
• Ghost
• Game (control)
• Activity (main)
• Setup (for loading on the XO)

Group Members

Yasser Hernandez, Taylor Plimpton, Abel Rendon Jr, Dennis Rodriguez

Milestones

• Week 2 ( January 15th 2010 - January 22nd 2010 )
  • Get git working on git.sugarlabs.org
  • Finish adding details to the PacMath Wiki
  • Make a Sketch-Up for the game
  • E-mail Math4 Mailing List informing everyone about our project and ask for ideas and volunteers

• Week 3 ( January 22nd 2010 - January 29th 2010 )
  • Get all the code sections defined well
  • Split up code sections
  • Start initial basic coding
  • Test an initial simple blank screen

• Week 4 ( January 29th 2010 - February 5h 2010 )