First and foremost; it's better to do some playtesting before you release. It may be trite, but the amount of frustration building over at the Civ3 side of the Apolyton fence is just amazing. If this conflicts with the publisher schedule, then that's too bad for said schedule.
Anyway; and perhaps more interestingly, the lesson Civ3 drives home is that if you are going to relay on AI automation to govern micromanagement tasks you'd better make _darn_ sure that AI is up to scratch. While the Civ3 worker automations is simply broken, at least as far as I'm concerned, I still have to option to do it by hand. That adds some amazing amount of late-game tedium, to be sure, but I still do it. I can't imagine the pain if all my workers were set on "shift-A" and I couldn't turn it off...
Those IFP govenors must be _way_ better than the Civ3 city govs and worker automation, or the frustration of watching the AI waste perfectly good resources will soon overpower all other parts of the game, however good they may be.
Anyway; and perhaps more interestingly, the lesson Civ3 drives home is that if you are going to relay on AI automation to govern micromanagement tasks you'd better make _darn_ sure that AI is up to scratch. While the Civ3 worker automations is simply broken, at least as far as I'm concerned, I still have to option to do it by hand. That adds some amazing amount of late-game tedium, to be sure, but I still do it. I can't imagine the pain if all my workers were set on "shift-A" and I couldn't turn it off...
Those IFP govenors must be _way_ better than the Civ3 city govs and worker automation, or the frustration of watching the AI waste perfectly good resources will soon overpower all other parts of the game, however good they may be.
Comment