Originally posted by Mike B. FIRAXIS
Selecting "New Game" is a shortcut for selecting "Load Scenario" and choosing civ3mod.bic. I also recommend you never modify this file. Scenarios are identical to so-called "real games." Any bug you saw in a scenario is specific to the scenario you were playing or it exists throughout the game. The barbarian bug you mentioned was probably caused by having the barbarian level set to sedentary in the scenario (it's easy to get this to happen without realizing it). By the way, the game does know when you've modified civ3mod.bic and marks it as a "scenario" anyway...
Thanks, for posting, Mike.
I can see why changing civ3mod.bic might lead to trouble if you are not careful. Maybe I'll change the file attribute to "read only," but I would have to remember to restore the "write" attribute when I installed a new patch. Nah, I'll just leave the file attributes alone.
The bug was not caused by setting barbs to "sedentary." It was set to "roaming." etj4Eagle observed the same thing and did verify that barbs were set to "roaming" in his scenario (and I sanity checked my scenario). And it did not occur in games started with "New Game." Based on what you said, I think it's probably related to generating a map in the editor. I'll post a saved game if anybody is interested.
But "New Game" has not always been a shortcut for "Load Scenario"->civ3mod.bic, because
in earlier patches when you changed civ3mod.bic the changes applied to games in progress that were started with "New Game" but this did not apply to "scenarios."
So you can see why some of us are in the habit of modifying civ3mod.bic. I'll try "Load Scenario" next time I start a game. Sounds like a useful tip.
So thanks for the tip, warpstorm, and thanks again for coming to see us, Mike.
But to tell the truth I really don't trust maps generated in the editor. I suppose that I'll rename the buggy .bic file civ3mod.bic and make sure the bug is still there after "New Game."