48
edits
Changes
Initial addition of most elements of wiki
==Math Quest==
{{TOCright}}
===Project Description===
Math Quest is a Math Blaster inspired game (set in a fantasy environment rather then a space one) being developed for the Math4 Project. Like Math Blaster, Math Quest aims to be a game that combines conventional gameplay of several disciplines (platformer, shoot 'em up, etc) in very basic settings with math, to make an educational game that is actually fun to play, not just educational. Even if it only delivers 50%-75% of the educational value of a full 'educational game', the increased playability leads to greatly increased playtime which negates that drawback, as well as instilling a general liking for math that lasted me several years.
===Goals===
*At least 5~10 different levels, with varying difficulty and length (some being more complicated then others). Each level will utilize a different gameplay genre, such as platformer, puzzle, etc.
*Picture-based storyline to tie levels together without relying on large amounts of text
*Ability to save and load progress
*Balance gameplay based on testing with 8-11 year olds
*Integrate at least 10 different Mass 4th grade standards into the gameplay.
===Levels===
The game includes a variety of levels of different sizes, each covering different math standards.
=====Bridge Building Level=====
*4.N.18 - Use concrete objects and visual models to add and subtract common fractions.
The player is tasked with building a bridge. Presented with pieces of wood of various sizes, the user must use the exact amount to complete the bridge.
=====Map Level=====
A map of the area is shown and the player must identify the coordinates where the tower is located.
=====Tower Gate Level=====
*4.N.1 - Exhibit an understanding of the base ten number system by reading, modeling, writing, and interpreting whole numbers to at least 100,000; demonstrating an understanding of the values of the digits; and comparing and ordering the numbers.
*4.N.14 - Demonstrate in the classroom an understanding of and the ability to use the conventional algorithms for addition and subtraction (up to five-digit numbers), and multiplication (up to three digits by two digits).
*4.P.1 - Create, describe, extend, and explain symbolic (geometric) and numeric patterns, including multiplication patterns like 3, 30, 300, 3000, ….
=====Tower Level=====
*4.N.2 - Represent, order, and compare large numbers (to at least 100,000) using various forms, including expanded notation, e.g., 853 = 8 x 100 + 5 x 10 + 3.
*4.N.11 - Know multiplication facts through 12 x 12 and related division facts. Use these facts to solve related multiplication problems and compute related problems, e.g., 3 x 5 is related to 30 x 50, 300 x 5, and 30 x 500.
*4.N.13 - Divide up to a three-digit whole number with a single-digit divisor (with or without remainders) accurately and efficiently. Interpret any remainders.
=====Watch Level=====
*4.M.3 - Identify time to the minute on analog and digital clocks using a.m. and p.m. Compute elapsed time using a clock (e.g., hours and minutes since…) and using a calendar (e.g., days since…).
The player is presented with two different watches (one being broken and one representing the current time), and they must calculate the amount of time that has elapsed since the watch broke.
===Tentative Milestones===
====Week 1:====
#Learn capabilities of XO laptop, Pygame
#Storyboard basic game design/story
#Begin planning architecture of game
====Week 2:====
#Prototype and start implementing game architecture
#Continue design of game
#Begin selecting 4th grade math standards to fit into levels
====Week 3: ====
#Finish general game architecture
#Finalize first pass on game story/design
#Begin prototyping first level code
#Start general UI graphics
====Week 4:====
#Tie in basic UI graphics
#Implement first level code
#Begin prototyping second level
====Week 5:====
#Finalize first level code
#Code second level
#Prototype 3rd level
#Implement graphics for first level
====Week 6====
#Implement graphics for second level
#Code 3rd level
#Prototype 4th and 5th levels
====Week 7====
#Implement graphics for 3rd and 4th levels
#Code 4th level
#Balance/testing with 8-11 year olds for initial levels
====Week 8====
#Code and graphics for 5th level
#Second pass on UI design/graphics
#Bug fixes on first four levels
====Week 9====
#Second pass on all level graphics
#Bug fixes on all levels and UI
#Balance/testing with 8-11 year olds
====Week 10====
#General polish pass on all elements of the game
#Final bug fixes
#Final balance/gameplay changes
#Teacher documentation
#Gameplay FAQ
===Contacts===
[[User: EricMallon |Eric Mallon]] (Team Lead):
ericmallon@sugarlabs.org
[[User:Eldrac |Tyler Bragdon]]:
tylerb@sugarlabs.org
{{TOCright}}
===Project Description===
Math Quest is a Math Blaster inspired game (set in a fantasy environment rather then a space one) being developed for the Math4 Project. Like Math Blaster, Math Quest aims to be a game that combines conventional gameplay of several disciplines (platformer, shoot 'em up, etc) in very basic settings with math, to make an educational game that is actually fun to play, not just educational. Even if it only delivers 50%-75% of the educational value of a full 'educational game', the increased playability leads to greatly increased playtime which negates that drawback, as well as instilling a general liking for math that lasted me several years.
===Goals===
*At least 5~10 different levels, with varying difficulty and length (some being more complicated then others). Each level will utilize a different gameplay genre, such as platformer, puzzle, etc.
*Picture-based storyline to tie levels together without relying on large amounts of text
*Ability to save and load progress
*Balance gameplay based on testing with 8-11 year olds
*Integrate at least 10 different Mass 4th grade standards into the gameplay.
===Levels===
The game includes a variety of levels of different sizes, each covering different math standards.
=====Bridge Building Level=====
*4.N.18 - Use concrete objects and visual models to add and subtract common fractions.
The player is tasked with building a bridge. Presented with pieces of wood of various sizes, the user must use the exact amount to complete the bridge.
=====Map Level=====
A map of the area is shown and the player must identify the coordinates where the tower is located.
=====Tower Gate Level=====
*4.N.1 - Exhibit an understanding of the base ten number system by reading, modeling, writing, and interpreting whole numbers to at least 100,000; demonstrating an understanding of the values of the digits; and comparing and ordering the numbers.
*4.N.14 - Demonstrate in the classroom an understanding of and the ability to use the conventional algorithms for addition and subtraction (up to five-digit numbers), and multiplication (up to three digits by two digits).
*4.P.1 - Create, describe, extend, and explain symbolic (geometric) and numeric patterns, including multiplication patterns like 3, 30, 300, 3000, ….
=====Tower Level=====
*4.N.2 - Represent, order, and compare large numbers (to at least 100,000) using various forms, including expanded notation, e.g., 853 = 8 x 100 + 5 x 10 + 3.
*4.N.11 - Know multiplication facts through 12 x 12 and related division facts. Use these facts to solve related multiplication problems and compute related problems, e.g., 3 x 5 is related to 30 x 50, 300 x 5, and 30 x 500.
*4.N.13 - Divide up to a three-digit whole number with a single-digit divisor (with or without remainders) accurately and efficiently. Interpret any remainders.
=====Watch Level=====
*4.M.3 - Identify time to the minute on analog and digital clocks using a.m. and p.m. Compute elapsed time using a clock (e.g., hours and minutes since…) and using a calendar (e.g., days since…).
The player is presented with two different watches (one being broken and one representing the current time), and they must calculate the amount of time that has elapsed since the watch broke.
===Tentative Milestones===
====Week 1:====
#Learn capabilities of XO laptop, Pygame
#Storyboard basic game design/story
#Begin planning architecture of game
====Week 2:====
#Prototype and start implementing game architecture
#Continue design of game
#Begin selecting 4th grade math standards to fit into levels
====Week 3: ====
#Finish general game architecture
#Finalize first pass on game story/design
#Begin prototyping first level code
#Start general UI graphics
====Week 4:====
#Tie in basic UI graphics
#Implement first level code
#Begin prototyping second level
====Week 5:====
#Finalize first level code
#Code second level
#Prototype 3rd level
#Implement graphics for first level
====Week 6====
#Implement graphics for second level
#Code 3rd level
#Prototype 4th and 5th levels
====Week 7====
#Implement graphics for 3rd and 4th levels
#Code 4th level
#Balance/testing with 8-11 year olds for initial levels
====Week 8====
#Code and graphics for 5th level
#Second pass on UI design/graphics
#Bug fixes on first four levels
====Week 9====
#Second pass on all level graphics
#Bug fixes on all levels and UI
#Balance/testing with 8-11 year olds
====Week 10====
#General polish pass on all elements of the game
#Final bug fixes
#Final balance/gameplay changes
#Teacher documentation
#Gameplay FAQ
===Contacts===
[[User: EricMallon |Eric Mallon]] (Team Lead):
ericmallon@sugarlabs.org
[[User:Eldrac |Tyler Bragdon]]:
tylerb@sugarlabs.org