Originally posted by wrylachlan
...I think that the total number of units in Civ3 gets to be a problem, and workers are no exception. ...
...I think that the total number of units in Civ3 gets to be a problem, and workers are no exception. ...
Remember how slow Civ3 when it first came out? Someone forgot to do the math.
Here's the deal: IIRC, you have a 256 x 256 map for 65,536 tiles. Say 30,000 are land. The idea is to develop as much land as possible and conquer the world, so let's imagine a point where you've got 20,000 tiles conquered. You might have 200 workers repairing battle damage, building rails, cleaning pollution etc. What Civ3 originally did was look at each worker going dig, dig, dig for about a second. Ok, 200/60 = over 3 minutes PER TURN of dig, dig, dig. Mind numbingly boring! Later patches spent less time looking at workers going dig, dig, dig; but it still really slows the game down. And if you want still bigger maps....
So:
1. Big maps
2. Reasonable turn times
3. Workers
Pick TWO.
I'll take 1 and 2, and shed no tears for stupid workers that are often doing the wrong thing, very, very slowly. In my opinion, of course.
Comment