Game Design
Hey,
Status:
I am designing a game for a competition(Technology Student Association). I am currently learning the C++ language and plan on using OpenGL. The game submission is DUE in April.
Problem:
I am not clear on the steps to design a game. This goals of this game is to be rated-E, have 5 levels, and be intellectually chanllenging. The game is to be somewhat like Striker 1945, visually. And as challenging as Metal Gear on the SNES.
At my level I do not plan on creating any artifical intelligence. I'll most likely will stick to collision barriers and if-statements for right now. In my senior year in high school I might consider artificial intelligence. Sometimes next month I will be enrolled in FLVS Computer Programming I and then AP Computer Sciences; but as it stands I am a beginnering in computer programming.
Comment:
I understand making a game is alot of work, but this game is goaled to be simple.
I have at least an hour a day to dedicate to this project with learning.
Any help would be appreciated! Thanks.
Status:
I am designing a game for a competition(Technology Student Association). I am currently learning the C++ language and plan on using OpenGL. The game submission is DUE in April.
Problem:
I am not clear on the steps to design a game. This goals of this game is to be rated-E, have 5 levels, and be intellectually chanllenging. The game is to be somewhat like Striker 1945, visually. And as challenging as Metal Gear on the SNES.
At my level I do not plan on creating any artifical intelligence. I'll most likely will stick to collision barriers and if-statements for right now. In my senior year in high school I might consider artificial intelligence. Sometimes next month I will be enrolled in FLVS Computer Programming I and then AP Computer Sciences; but as it stands I am a beginnering in computer programming.
Comment:
I understand making a game is alot of work, but this game is goaled to be simple.
I have at least an hour a day to dedicate to this project with learning.
Any help would be appreciated! Thanks.
Last edited on
What are the rules around this? Can you adapt an existing game engine? That would be where I would start. Happy Penguin should provide ample options for open source programs that are similar (vertical or side scroller) that can be adapted to your needs. If you can't use it directly, it would still help to dig in and understand how it works. You might even engage the author(s); ask them about design decisions, what they would do differently today, etc.
Search for "vertical scroller" here: http://www.happypenguin.org/
Search for "vertical scroller" here: http://www.happypenguin.org/
REGULATIONS
A. The game segment must be turned in on a DVD.
B. The game must execute and be played directly from the DVD.
Entries will be evaluated using only a PC platform. Participants
will not be permitted to install anything onto the evaluator’s
computer.
C. Instructions and text must be clear and understandable for the
evaluation process.
D. Entries must be a team project.
E. Notebooks and DVDs become the property of TSA, Inc.
F. The game must include original work of the team, but game
architecture, game engines, graphics and sounds may be used
from other sources. Work that is not created by the team must
have proper documentation showing copyright permissions and/
or license for usage in the game.
G. The DVD and an 8½" X 11" notebook must be submitted. The
notebook must be a standard three (3)-ring binder, with a clear
front sleeve for a cover page. The cover page must include the
event title, the conference city and state, and the year. The inside
of the binder must include the following single-sided, 8½"X 11"
pages:
1. Title page with the event title, the conference city and state,
and the year; one (1) page
2. Table of contents
3. Purpose and description of game, including target audience;
one (1) page
4. A detailed explanation of how to play the game, including a list
of all control functions; pages as needed.
5. Team’s self-evaluation of the design process that includes use
of event evaluation criteria; one (1) page
6. A hand-drawn storyboard; pages as needed
7. List of hardware and software used in development of the
game, as well as cost of development; pages as needed
8. List of references that includes sources for materials
(copyrighted and otherwise); pages as needed
9. Permission letters for copyrighted material; pages as needed
10. A list of everything in the game not created by the team; pages
as needed
11. Plan of Work log that indicates preparation for the event, as
noted by date, task, time involved, team member responsible
and comments (see Plan of Work log); one (1) page.
A. The game segment must be turned in on a DVD.
B. The game must execute and be played directly from the DVD.
Entries will be evaluated using only a PC platform. Participants
will not be permitted to install anything onto the evaluator’s
computer.
C. Instructions and text must be clear and understandable for the
evaluation process.
D. Entries must be a team project.
E. Notebooks and DVDs become the property of TSA, Inc.
F. The game must include original work of the team, but game
architecture, game engines, graphics and sounds may be used
from other sources. Work that is not created by the team must
have proper documentation showing copyright permissions and/
or license for usage in the game.
G. The DVD and an 8½" X 11" notebook must be submitted. The
notebook must be a standard three (3)-ring binder, with a clear
front sleeve for a cover page. The cover page must include the
event title, the conference city and state, and the year. The inside
of the binder must include the following single-sided, 8½"X 11"
pages:
1. Title page with the event title, the conference city and state,
and the year; one (1) page
2. Table of contents
3. Purpose and description of game, including target audience;
one (1) page
4. A detailed explanation of how to play the game, including a list
of all control functions; pages as needed.
5. Team’s self-evaluation of the design process that includes use
of event evaluation criteria; one (1) page
6. A hand-drawn storyboard; pages as needed
7. List of hardware and software used in development of the
game, as well as cost of development; pages as needed
8. List of references that includes sources for materials
(copyrighted and otherwise); pages as needed
9. Permission letters for copyrighted material; pages as needed
10. A list of everything in the game not created by the team; pages
as needed
11. Plan of Work log that indicates preparation for the event, as
noted by date, task, time involved, team member responsible
and comments (see Plan of Work log); one (1) page.
Topic archived. No new replies allowed.