Video Game Design/Process
From Wikibooks, the open-content textbooks collection
Contents |
[edit] Resources
Consider your resources, what abilities do you personally have? Can you program, draw, and render a polygon? How much money do you have and how much time are you going to spend on it? Do you have the technology to build a game or do you need to get it? Do you know what you need?
[edit] Teamwork
A video game is a really big project for someone to take on, especially just one person. It may be a good idea to do the project as a team bringing together all the resources you need to put together a good video game. It is almost impossible for only one person to create a game that people will actually enjoy. Being in game development requires you to have good social skills, because 99% of the time you'll be working with a team of designers. It's important that you build a friendly relationship with your fellow game designers to get the best results of a project.
[edit] Concept vs. Ability
Finally, before you begin developing remember to discern between what you want to do, and what you actually can do. Figure out the resources that you have and compare them with the resources the project will require and adjust accordingly. If you have a lot of resources but your concept is simple, perhaps you could expand it. And if you have a complicated concept but simple resources, maybe you need to expand your resources.
After you have gone through all of these considerations outline the project, first by how the game will work and how it is arranged then chronologically by how you are going to accomplish those things - it might be helpful to set a due date for yourself.
[edit] Testing and Development Phase
The testing and development phase are where the game is actually created. As you program, make graphics, compose music and collaborate these resources you will have a lot of testing and debugging to to do. Consider the following sections.
