challenge -> (11/6/2001 2:31:00 AM)
|
The two lists posted by Paul and Ludovic are excellent, but before you start setting up the standards and conventions needed to keep an open source development project uniform, you still need a game concept.
The preliminary concept staement does not need to be drastically detailed, but if you don't know what you're trying to build, you won't know what parts you need. To refer to Duane's earlier statement of not needing to be a mechanic to design a car: if you think you're building a race car, and someone else thinks you're building a railway car, the wheels ain't gonna fit.
One the primary tools of game design is the concept statement. When planning a source book for an existing RPG, for example, the game company I worked for required an outline of intended material, how the material and information would be integrated into the existing game, and a sample chapter so editors could get a feel for the presentation of the material.
the same, modified for the medium, is probably a useful tool for the open source format.
|
|
|
|