Tuesday, November 22, 2011
Sunday, November 20, 2011
CRITERION C PLAN
PLAN THE PRODUCT / SOLUTION:
Step One
Task:Create My World (Create the Maze) Due Date: 18-11-11
Process: I am going to use Kodu as my platform to create my video game. First I am going to start out with making my world, which would basically just be a maze. The first thing I am going to do is figure out a good, complicated maze. I would create a surface large enough to cover it, then use the walls to create the maze.
Step Two
Task: Creating my player and formatting it (actions) Date due: 28-11-11
Process: Next I will create a player, and its physical appearance. Then I will chose its actions. When to turn, when to eat, and when it'll stop.
Step Three
Task: Choosing the different types of music that I could insert into my game Date due: 1-12-11
Process:I would pick out a couple different types of music, one for indicating the correct path, which would generally be a happy kinda of music (major tonality) and the other indicating that your going on the wrong path which would be sad, angry music (minor tonality).
Step Four
Task: Inserting the Music in my game Date due:5-12-11
Process: The next step would be to insert the music into my game, and format it according to where the character does move.
Step Five
Task: Testing out the game Date due:6-12-11
Process: This task would include testing out the game, weather the characters are working, if the game is running as its supposed to or not.
USE APPROPRIATE TOOLS AND TECHNIQUES: Discuss the tools available and used. What did you do to develop your skills with these tools?
To make the game, I used Kodu. Kodu was simple to create a game in because everything was simple and clear to follow. I experimented a lot, and explored the game to see what things the game did, or allowed you to put, into your creation, and what type of games you can make.
FOLLOW THE PLAN:
Evaluate & reflect on your plan. Describe modifications have you made as you proceeded.
Evaluate & reflect on your plan. Describe modifications have you made as you proceeded.
Sunday, November 13, 2011
Evaluate: Questions
Original Questions:
1. What are the good points about the game?
2. What are the bad points about the game?
3.How useful is the game?
4. How was your game platform (Kodu)?
5. Please list some improvements.
After I read most of my classmates evaluations I saw that my game was pretty much pointless and hardly taught anyone anything, which was not too surprising, because I never really put anything in the game to teach anyone, even though my intention was to teach people about music. I could've done many other things in my game to have made it better, and my classmates suggested many things, which I did put after reading all the evaluations (dieing when you walk on the grass). I myself found that the game was way too easy. The only thing that I did like was the fact that I succeeded in things like programing characters and making them talk :) In my final product my maze looked really unorganized and sketchy, this was because I made the game in 10 mins, due to the fact that my game got erased on the day of submission. For me the good points of the game was the way I formatted my main players. The player giving you instructions made it easier for the person playing to follow the game. Kodu was an really easy platform to use for making games. Sometimes it was frustrating to use it like the times that it started getting too slow because there were too many things in my world, but all in all it was good.
Jacky:
1. What are the good points about the game?
The idea with the maze was really good and unique and could be a good basic principle for an actual game. The "helper"-Kodu at the beginning who explained what to do was really helpful.
2. What are the bad points about the game?
Kodu can move outside the maze, too.
3. How useful is the game?
You learn how to navigate and orientate oneself.
4. How was your game platform (Kodu)?
The interface was really nice and kodu easy to navigate through the game.
5. Please list some improvements.
Maybe it would be good to program Kodu so that he can't move outside the path, otherwise it makes it easy to cheat.
1. What are the good points about the game?
2. What are the bad points about the game?
3.How useful is the game?
4. How was your game platform (Kodu)?
5. Please list some improvements.
After I read most of my classmates evaluations I saw that my game was pretty much pointless and hardly taught anyone anything, which was not too surprising, because I never really put anything in the game to teach anyone, even though my intention was to teach people about music. I could've done many other things in my game to have made it better, and my classmates suggested many things, which I did put after reading all the evaluations (dieing when you walk on the grass). I myself found that the game was way too easy. The only thing that I did like was the fact that I succeeded in things like programing characters and making them talk :) In my final product my maze looked really unorganized and sketchy, this was because I made the game in 10 mins, due to the fact that my game got erased on the day of submission. For me the good points of the game was the way I formatted my main players. The player giving you instructions made it easier for the person playing to follow the game. Kodu was an really easy platform to use for making games. Sometimes it was frustrating to use it like the times that it started getting too slow because there were too many things in my world, but all in all it was good.
Jacky:
1. What are the good points about the game?
The idea with the maze was really good and unique and could be a good basic principle for an actual game. The "helper"-Kodu at the beginning who explained what to do was really helpful.
2. What are the bad points about the game?
Kodu can move outside the maze, too.
3. How useful is the game?
You learn how to navigate and orientate oneself.
4. How was your game platform (Kodu)?
The interface was really nice and kodu easy to navigate through the game.
5. Please list some improvements.
Maybe it would be good to program Kodu so that he can't move outside the path, otherwise it makes it easy to cheat.
1) I like that theirs a path
2)the kudo can cut across the path to get to the finish point
3) navigational skills
4) it was very colorful
5) allow the kudo to only stay in the blue path.
- Sonia
4. good looking and easy and tough at the same time.
add some new challenges
not entirely sure what it's teaching me
Thursday, November 3, 2011
Video Games Idea
- My idea for my video game is based on music tonality. So through my game I will teach people about how music can tell you about the different situations you are in. So a Minor tonality would mean that you are in a bad situation, and Major would mean your in a good one.
I was thinking of doing something like a maze, where the music would guide you to the right direction and when you are given two different directions then you have to listen to the 2 types of music and figure out which one is right, and leads you towards the end of the maze.
This game is created for all the people who know very little about music, or cannot distinguish the difference between sad. depressing, angry type of music, or happy and peppy types of music. basically major & minor music.
Another idea that I had was games on Interior or Exterior Home Decor. I chose to do Music over this one,because I know more about music than Home Decor.
I was thinking of doing something like a maze, where the music would guide you to the right direction and when you are given two different directions then you have to listen to the 2 types of music and figure out which one is right, and leads you towards the end of the maze.
This game is created for all the people who know very little about music, or cannot distinguish the difference between sad. depressing, angry type of music, or happy and peppy types of music. basically major & minor music.
Another idea that I had was games on Interior or Exterior Home Decor. I chose to do Music over this one,because I know more about music than Home Decor.
Subscribe to:
Comments (Atom)