quote: Originally posted by supremus on 03-08-2001 03:40 PM This kind of behavior is exactly what the companie's developer wait from the gamers. That's the less expensive way to make patches and keep customers happy. Launch unfinished products in the market place, wait some weeks for the fanatics gamers to find out bugs and then making patches. That's the way thigs are and they only will change when game buyers start to be as demanding as more mature markets buyers. |
I disagree strongly. As someone who writes software for a living, I can attest that even the best designed and tested software will exhibit bugs when it reaches end users. It's impossible to test every possible combination of inputs to a complex program. None of the items on the Civ2 bug list is a game-breaker (obviously, since it's still being played 5 years later), and some might be considered design decisions rather than bugs.
I'd agree with Ming and Yin that there will probably be a narrow window of opportunity where Firaxis will make patches in response to (politely worded) lists of bugs and "misfeatures". The wider this window, the better the end product will be. But it's an economic decision for Firaxis: how many programmer hours do they spend improving the game from salable to perfect? We at Apolyton hope the answer is "a lot", but the guys in the green eyeshades are going to want to see some return on that investment of time and money. Do they get $100,000 in sales if the Apolyton team is made completely happy? I doubt it...
From what I hear about CTP2, some dedicated souls on Apolyton are trying to fix problems by using the scripting language: if Civ3 has something similar, that's probably the only answer to long-term maintenance of the software. If someone discovers a killer strategy after the game's been out for six months, Firaxis is not going to go back to patch the holes. But some fanatic at Apolyton might.
Comment