Reg Pither
Warlord
I never build a worker or settler first as I always let the city grow to 2 or 3 population before doing so. Warriors/barracks first every time for me.
Settler vs Worker
- Thread starter Darcia
- Start date
Tavenier
King
Depends on what techs I start with. If I start with tile-improving techs like mining, the wheel or agriculture, then I build a worker in the first turn. Because the first techs I research are always to found religions, and they don't have tile-improvements.
Skanderbeg
Chieftain
Depends on the situation, but usually:
Warrior
Prebuilding warrior until city grows to size two
Worker
Completing warrior
(sometimes, if it takes only a few turns: Prebuilding barracks or Stonehenge untils city grows to size three)
settler
stonehenge or barracks or warrior/settler (mostly Stonehenge)
Prince Level
Warrior
Prebuilding warrior until city grows to size two
Worker
Completing warrior
(sometimes, if it takes only a few turns: Prebuilding barracks or Stonehenge untils city grows to size three)
settler
stonehenge or barracks or warrior/settler (mostly Stonehenge)
Prince Level
Depends a little on the situation, but more often than not I'll build the settler first (monarch level). The reason is that I'm currently playing with a strategy of grabbing early religions, and that means that my first research techs don't give me many worker actions. So if I built a worker first there wouldn't be much it could do.
Zombie69
Emperor
- Joined
- Nov 22, 2005
- Messages
- 1,902
Never build the settler first unless going for early religions, and never go for early religions at high difficulty levels.
It's always much more efficient to chop rush the settler with a worker or two.
The first build could be a worker, a warrior, a scout, a barracks, anything, but not a settler.
It's always much more efficient to chop rush the settler with a worker or two.
The first build could be a worker, a warrior, a scout, a barracks, anything, but not a settler.
If I start with Agriculture or Mining then: Worker/ Chop Warrior *2 / Chop Settler
City Growth isnt so important imo. If you have enough forests to justify chopping a settler/worker then why wait? One forest will get you 2 warriors, so if you have a surplus of forests then chop em all and turn them into little baby Warriors.
Diff: Monarch
City Growth isnt so important imo. If you have enough forests to justify chopping a settler/worker then why wait? One forest will get you 2 warriors, so if you have a surplus of forests then chop em all and turn them into little baby Warriors.
Diff: Monarch
Zombie69 said:
On monarch, I find going for early religion can work quite well, not least because some very useful wonders are on the same path as the religions - you end up by about 1AD extremely cultured but small-ish and militarily weak compared to the AI - but with good military tactics it's not too hard to turn that around.
I've not tried early religion on emperor or above, but I strongly suspect you're correct, and that on those levels going for religions first will leave you just _too_ weak (and you'll probably miss the religions anyway).
- Warrior
- Worker (when I obtain size two in the city, while don't, another warrior)
- Worker (finishing previous warrior during the turns that no extra hammers are received from chopping)
- Settler
- Warrior
- Worker
- Great Wonder
That is the way normally I begin. Perhaps if you want to found a religion you should wait a little to create worker until you have bronze working, but normally it is my first research, if I have mining, of course (I don't care too much to found religions...).
Level: last 2 games in Monarch (winning by diplomatic and points
)
- Worker (when I obtain size two in the city, while don't, another warrior)
- Worker (finishing previous warrior during the turns that no extra hammers are received from chopping)
- Settler
- Warrior
- Worker
- Great Wonder
That is the way normally I begin. Perhaps if you want to found a religion you should wait a little to create worker until you have bronze working, but normally it is my first research, if I have mining, of course (I don't care too much to found religions...).
Level: last 2 games in Monarch (winning by diplomatic and points
)
Zombie69
Emperor
- Joined
- Nov 22, 2005
- Messages
- 1,902
Emperor and above i would call high difficulty levels because that's when the AI bonuses really start piling up. Doesn't mean you can't win there, or that they're even really hard to win actually, but the top 3 of 9 difficulty levels seem to me to qualify as "hard difficulty levels", the bottom 3 being easy and the medium 3 being, well, medium!
Like many others here it depends on the situation, but most often it is a couple of warriors (defense and exploration for goodie huts), then a worker, then settler. Maybe do settler first if I need to get the second city started quicker. I always wait until city is at least size 2, and most often size 3 before I start with the workers and settlers.
Great_Scott
aka Cottus Arci
Darcia said:
I never chose Worker or Settler in the first turn. Since producing a worker or settler halts your city growth, I prefer to wait until the city has reached population size 3.
Normally, I build a barracks... or a work boat if i'm close to fish/clams
Zombie69 said:
Out of interest (and apologies about the topic drift): A lot of people (and I'm inclined to agree) seem to say that monarch is a pretty big jump up from prince in difficulty, changes to strategy etc. - much bigger than the noble-prince jump. Would you say the same is true of the monarch-emperor and later jumps, or are they more like gentle increases in difficulty?
jar2574 said:
Unless you don't have Bronze Working yet, and then the worker won't have much to do. Especially the case if you are working towards an early religion or don't have mining to start with. Also doesn't work all that well if you only have one or two forest tiles in reach.
Besides, I'd much rather have a few warriors around to protect the worker from barbs. Usually by the time I have a few of them, the city is at 2 or three and ready to build the worker.
Similar threads
