Barbarians at work (barbarian worker blob of death)

[DaveGold]

I've a feeling there's a bug here somewhere.

What I guess is happening is that the city state is producing workers and the barbarians kept capturing them. So the city state made more workers and the barbarians captured some more. Then some wandering AI nation caravel came past and killed the barbarians but not the workers, so the workers are wandering about.I wouldn't like to say what the bug is but there's clearly something nonsensical going on.

 

[dexters]

That's a free ticket to free alliance renewals with Bucharest. Just capture and return 1 worker every 5-10 turns.

 

[Stecker]

In my game the silly barbarian parked the worker I just wanted to free in the water.

Thus making it impossible to free the worker and also effectively blocking my way in the shallow waters as I didn't wanted to shoot the worker and waited that he may go back on land again but he didn't. I stopped playing by now and are waiting for some highly needed fixes.

 

[Tyrael]

I recall reading a theory somewhere that the AI's values (called flavors?) for things like expansion and military can sometimes cause them to always desire a worker before a military unit. It then builds a worker and starts on something else, but when its worker gets captured it re-evaluates the situation and realizes "hey, I have no worker! I want a worker first!" so it builds a worker. Repeat ad nauseum.

Somewhat unrelated- I've also read that the AI tries to specialize its cities as growth, military, etc. So sometimes it will specialize its capitol to not prioritize expansion, so if its first settler gets killed it will never build a settler again since its second city was going to be expansion specialized, so the cap focuses on other things. The AI just never reevaluates in consideration of the fact that said second city doesn't exist and never will.

 

[dexters]

I recall reading a theory somewhere that the AI's values (called flavors?) for things like expansion and military can sometimes cause them to always desire a worker before a military unit. It then builds a worker and starts on something else, but when its worker gets captured it re-evaluates the situation and realizes "hey, I have no worker! I want a worker first!" so it builds a worker. Repeat ad nauseum.

Somewhat unrelated- I've also read that the AI tries to specialize its cities as growth, military, etc. So sometimes it will specialize its capitol to not prioritize expansion, so if its first settler gets killed it will never build a settler again since its second city was going to be expansion specialized, so the cap focuses on other things. The AI just never reevaluates in consideration of the fact that said second city doesn't exist and never will.

I've noticed this with a game I played against the Ottmans. took his first settler and he OCCed for the next 40 turns, until I dow and took his capitol. He may have settled eventually.

Had a similar situation with Persia where I captured his first expansion city, but he eventually expanded his empire. I was too busy consolidating montezuma's lands.