Jump to content
Posted 19 June 2000 - 01:42 PM
Posted 19 June 2000 - 01:54 PM
Posted 19 June 2000 - 02:39 PM
Original post by BigBlueMonkey
Yes, absolutely. Because of the pace that technology is advancing, there are always new and better ways of doing things, and as the technology level increases, it makes ideas previously thought to be too complex a reasonable goal.
I''ve made a couple programs, and a couple games, and no matter how long I worked on them, I always come up with new ideas for things I can do.
So, to sum it all up, I would say that game design is an art, and production of a game can conceivably go on forever (if the project is worth it)
Posted 20 June 2000 - 12:58 AM
Posted 20 June 2000 - 02:04 AM
Original post by Kylotan
When the game is published, the game design is complete. Any lingering ideas for add-ons or modifications become the game design for the sequel
Seriously: game design, and to a lesser extent software design, is an evolutionary and self-modifying process. Unlike the strict "analysis-design-implementation-testing-maintenance" model often stated by academics. Each major piece of software tends to include its own Research and Development. This is a shame for the industry, as separate, dedicated research would improve the state of play - but in the real world, developer teams are having to learn as they go along. Sometimes they find a better way of doing something, so the design must change. Sometimes they find something is impossible, so the design must change. Sometimes design follows implementation rather than the other way around ("we have 2 free bits, can we think of another 2 monster AI flags?"). This would seem ''wrong'' to someone who believes in rigid design, but would seem right to the guy who wants to get as much game as possible out of that computer. Another common effect is where you can''t quite fit the specification: but you can fit 90% of it if you make a small change elsewhere A very basic example is having to cut down the number of frames of animation so that you can store them in a byte-indexed array. Again, the design evolves to fit the specification.
The only design that is not going to change, where you have control over such changes, is a design that it is either being done as an academic exercise, or is so loose to be almost useless. Design and Implementations are 2 sides of the same coin, inextricably intertwined and as one changes, so will the other.
Posted 20 June 2000 - 09:07 PM
Posted 20 June 2000 - 11:34 PM
Posted 21 June 2000 - 03:14 AM