Barathor
Emperor
- Joined
- May 7, 2011
- Messages
- 1,202
I've always felt that the barbarians hurt the AI much more than the human player, which is why I avoid settings like Raging Barbarians. Even though it would be quite fun initially, I'd be left with poorer AI opponents later on, after the rampaging.
But, I've been autoplaying a bunch of games to observe some things, and I'm shocked by how often the AI loses settlers to the barbarians. This almost never happens with the human player, but with the AI, I can almost say it's common.
In a standard game, you'll easily see 3-4 captured settlers between turns 40-50. You can even find a few earlier sometimes for the civs that fast expand. What's worse is that the AI doesn't even go after those camps to get their unit back.
Players often complain about how slow and stagnant the AI is, among other things. This is definitely one of the issues contributing to that. Behind the fog of war, those AI's actually are building settlers and trying to expand, they're just getting owned by the barbarians.
I got a kick out of this one when I saw it and took a quick screenshot:
Third time's a charm? Nope. At least Poland managed to take back one of them and settled their 2nd city. It only took maybe 20 to 25 turns to do so.
Granted, the issue is exacerbated here because of the land formation that Poland was placed on. It only allows for two land paths to move in and expand, creating a barbarian gauntlet to run through.
- - - - - - -
Besides making the AI smarter with these sort of things, and I know some players would hate the thought of this, but what if some additional rules were thrown in to help the AI in this situation? Such as, barbarians won't attack an AI settler. Most of it will be going on in the background anyway, and it would help ALL the AI's to get up and running faster during the early game.
Just think about how devastating it would be to lose your first settler that early. Most would just reload the game or start a new one, if a mistake like that was made early on. I believe few players would continue the game, say, "That's XCO... err... Civ, baby!", and keep playing while trying to rescue it before it becomes another worker for the AI.
But, I've been autoplaying a bunch of games to observe some things, and I'm shocked by how often the AI loses settlers to the barbarians. This almost never happens with the human player, but with the AI, I can almost say it's common.
In a standard game, you'll easily see 3-4 captured settlers between turns 40-50. You can even find a few earlier sometimes for the civs that fast expand. What's worse is that the AI doesn't even go after those camps to get their unit back.
Players often complain about how slow and stagnant the AI is, among other things. This is definitely one of the issues contributing to that. Behind the fog of war, those AI's actually are building settlers and trying to expand, they're just getting owned by the barbarians.
I got a kick out of this one when I saw it and took a quick screenshot:
Third time's a charm? Nope. At least Poland managed to take back one of them and settled their 2nd city. It only took maybe 20 to 25 turns to do so.
Granted, the issue is exacerbated here because of the land formation that Poland was placed on. It only allows for two land paths to move in and expand, creating a barbarian gauntlet to run through.
- - - - - - -
Besides making the AI smarter with these sort of things, and I know some players would hate the thought of this, but what if some additional rules were thrown in to help the AI in this situation? Such as, barbarians won't attack an AI settler. Most of it will be going on in the background anyway, and it would help ALL the AI's to get up and running faster during the early game.
Just think about how devastating it would be to lose your first settler that early. Most would just reload the game or start a new one, if a mistake like that was made early on. I believe few players would continue the game, say, "That's XCO... err... Civ, baby!", and keep playing while trying to rescue it before it becomes another worker for the AI.