Where did I go wrong?

Whatever, I'm done arguing the point. I barely play SP and I was able to kill Pacal by 40 AD and razed a Mongolian city not long after. I didn't really feel like proving I could conquer the whole continent because SP feels really boring to me; so, I'll leave it at that.

BTW, I should also point out that the speed the game was on was one I've never played so my worker management was terrible.

The two saves I have are the turn before I kill Pacal and the latter one is where I stopped caring and quit.
 

Attachments

I have no idea what SP is.

Also, warring is easier in lower level games, but for some reason it's harder to advise compared to more typical play, so I think people prefer expansion type advice.
 
SP is of course Single Player. Cashew's civ background is presumably in Multi Player and he goes for the build lots of units, kill everything and screw the economy approach. How well this would work is debatable and he gave up through boredom before he started running into problems such as attacking longbows behind city walls without seige weapons or espionage.
 
pigswill, I guess that is true, but the AI was still quite a bit away from longbows seeing as they didn't even have seige or walls. It's not like you don't come across longbows in multiplayer; I do know how to deal with them. The question is just whether I can get an econ that can support the number of catapults and other city raiders I will need.

To clarify, I am not a "screw the econ" approach guy. Obviously your economy is very important, but in my opinion people do many things that are frivolous at best in trying to support that economy. Realistically, a lot of cottages is all you will ever need to support a large army. All this fancy specialist crap and other things people try to do to get ahead are completely unnecessary. In unique game types such as one city challenge they might present some use, but the simplest and most direct approach is what I find to be most efficient in winning.
 
cashew: I had a look at your Afterwards save and played a couple of turns from it. In my opinion you are heading towards defeat. You've got no stack. Your units have already gone on strike once. Sury and the Khan declared on you. Your 2 axes outside the walled Monglian city have 2% chance. You have 3 lvl3 units, no medic to promote to a supermedic. Sury is colonising Pacal's old lands. Its going to take 6-8 turns before you can assemble your next stack. On Monarch you will be facing longbows well before 1000ad.
 
Whatever, I'm done arguing the point. I barely play SP and I was able to kill Pacal by 40 AD and razed a Mongolian city not long after. I didn't really feel like proving I could conquer the whole continent because SP feels really boring to me; so, I'll leave it at that.

BTW, I should also point out that the speed the game was on was one I've never played so my worker management was terrible.

The two saves I have are the turn before I kill Pacal and the latter one is where I stopped caring and quit.

Unfortunately, situation there is not good. One new city in Kublai's and Sury's culture pressure is all that killing Pacal gave. Technical situation is very poor. You don't have CoL or Currency, not even Mathematics or Alphabet. Both Kublai and Sury are annoyed, and they will probably go after you with knights when you are still in classical era. And for some reason you don't have a single spear to counter Kublai's keshiks. Playing just few turns more shows your axe army doesn't stand a chance. It can hardly keep your old cities and has no chance to take any from Kublai and keep it.

Probably this just shows that MP-tactics don't do well in SP on any higher levels.

edit: it wasn't quite so bad. With huge stack of axes, I was actually able to take Old and New Sarai (lost Mutal) and take peace. Technical situation is still awful and Sury can't be far from Feudalism (it's 760 and Monarch AI's sometimes get it at 200's).
 
I could have just choked more AIs. For some reason I got it into my head that I had to prove I could kill Pacal... I think it's because someone mentioned the original save's settling had to do with blocking off Pacal. Anyways, it was not difficult to choke out Pacal at all and I could have easily done the same to Sury and Genghis had I bothered. Then they would have been in the same basic situation as Pacal and not had jack crap to fight me with. I really hate games that are as slow as that (epic/marathon w/e that was) so I won't be doing it again but I am confident that if I had to play it again I'd have all 3 of those AI guys in the hole.

Oh, and I have no idea about diplomacy or any crap so the two of them being mad at me made no impression on me whatsoever since I planned on killing them anyways.
 
I grabbed the fish/pig city with a settler in my save, and with a few more cities it was losing 8 gpt. If you're not careful, pacal's land is far enough that it can sink your economy without a good economic base.
 
I think a SE makes perfect sense here. As I stated earlier, little commerce but good amount of food resources coupled with a huge area to settle and stone nearby. Running representation and scientists one can expand at a great pace and not care much about keeping the slider up. The philosophical trait also means faster GSs that can help out by bulbing some key techs. Warring is certainly viable as well but it's not exactly a rush here and that means you're doing the same sort of thing as the SE are doing, except you also have to put hammers into extra units instead of extra development/economy boosters and after killing Pacal you're a close neighbour to KK and Sury so then you have to extend even further.
 
Warring is certainly viable as well but it's not exactly a rush here and that means you're doing the same sort of thing as the SE are doing, except you also have to put hammers into extra units instead of extra development/economy boosters and after killing Pacal you're a close neighbour to KK and Sury so then you have to extend even further.

It wouldn't be any fun if there was only 1 person to kill :)
 
Back
Top Bottom