Introversion’s Mark Morris has written a piece on Building a Prototype.
Of course in different games, different aspects are more important (the story is perhaps less important in Half-Life than in Mass Effect), but you may not be able to determine this at the start. The point is that until you actually have the game in front of you, then you do not necessarily know which areas of the design work need tweaking, and which are fundamentally flawed.
This is where your prototype comes in…
Morris then takes you through the “spiral software engineering paradigm” that Introversion uses. The basics:
- Determine the scope of the prototype.
- Determine what part of the design is uncertain , important, or challenging.
- Hack something together.
- Once you have something working, do it again.
The above approach provides a good deal of momentum for your initial work. It enables you to tackle the hard problems first and not get caught up in something that might ultimately prove impossible.
Even though it is a good read, I wish it had some more meat on it. Specifically I would have loved to have seen some examples from the trenches when Darwinia, Uplink, and Defcon were in development.
[tags] indie, game development, video games, [/tags]