Prototyping, the act of creating an original model as a foundation for the end product, is an essential and efficient part of the game design process. Â It allows us to find out quickly what does and does not work which saves us time and money. Â Itâ€™s the time, before the game design has gone too far, when we set the rules and find the fun. Â Rapid prototyping saves money by letting us make less-costly mistakes early on and allowing us to bail on bad ideas much earlier in the process. Â It also teaches us about the game, making it easier to formulate project pitches and press releases. Â
The key to rapid prototyping is doing it quickly. Â This is not the time to build assets or large bits of code that will most likely get scrapped before the project even gets started. Â Prototype with borrowed assets, instead. Â Begin with a tabletop or paper version of the game. Â This will not feel the same as digital play will, but it will show the team weaknesses in the rule set and fun immediately with little expense in time and money. A game that lacks the essential elements of fun and great play mechanics wonâ€™t improve with fancy graphics and sound. Â The point of tabletop prototyping is to weed out this weakness. Â
A tabletop prototyping kit is easily put together. Â A vinyl hexagon mat with squares on the reverse side provides a game board which can be blocked off with masking tape. Â Keep on hand two sets of dungeon dice; playing cards; 3x5 cards; Â and items, such as glass stones and soda can tabs, to use as playing pieces. Â Block out your game and get it before people as soon as possible.
First Stage Prototyping
Itâ€™s important to stay flexible in all stages of prototyping. Â Use the 80/20 Rule.Â Brainstorm for every possibility and throw out 80 percent of the ideas. Â It is vital to avoid feature creep. Â
Begin to build the game using borrowed assets and bits of code. Â Pygame.org provides an open source language and games that you can change. Â Gamemaker utilizes drag-and-drop functionality so that you wonâ€™t have to write code or create art assets to start playing. Â Do not build a new engine or use one that only certain members of the team are familiar with. Â You want the first prototype up and in front of testers inside of one to two weeks. Â
If you donâ€™t have testers you donâ€™t know, use moddb.com to find testers. Â Take their comments with a grain of salt. Â All you really need to know is whether or not the game is viable as a full game.
Second Stage Prototyping
Once you have gleaned all that you can from the testers, it is time to begin replacing borrowed assets with real ones. Â Install improvements based on tester feedback. Always have a playable build; itâ€™s important to be able to play and test things. Â Remain flexible during this time; things will change daily.
Test again with a fresh group of testers. Â Using the original testers or any number of them will taint the results. Â
Begin to Build a Vertical Slice
Once you are confident that the game is a viable option, begin to build a level. Â This is what you will show to publishers and potential stake-holders. Â All work at this point should be original and the game must be fully functional. Â The programmers can start building tools now: Â artist tools, configuration files for rapid changes, and level editors. Â Polish. Â Get people excited about the project and start creating buzz. Â
Now, stop prototyping and make the game.Â ď»ż